This guide explains how to use the new date_added feature for tracking when skills were created or added to the collection.
The date_added field in skill frontmatter allows you to track when each skill was created. This is useful for:
- Versioning: Understanding skill age and maturity
- Changelog generation: Tracking new skills over time
- Reporting: Analyzing skill collection growth
- Organization: Grouping skills by creation date
The date_added field uses ISO 8601 date format: YYYY-MM-DD
---
name: my-skill-name
description: "Brief description"
date_added: "2024-01-15"
---python scripts/manage_skill_dates.py listOutput example:
📅 Skills with Date Added (245):
============================================================
2025-02-26 │ recent-skill
2025-02-20 │ another-new-skill
2024-12-15 │ older-skill
...
⏳ Skills without Date Added (5):
============================================================
some-legacy-skill
undated-skill
...
📊 Coverage: 245/250 (98.0%)
Add today's date to all skills that don't have a date_added field:
python scripts/manage_skill_dates.py add-missingOr specify a custom date:
python scripts/manage_skill_dates.py add-missing --date 2024-01-15Set a date for all skills at once:
python scripts/manage_skill_dates.py add-all --date 2024-01-01Update a specific skill's date:
python scripts/manage_skill_dates.py update my-skill-name 2024-06-15Generate a JSON report of all skills with their metadata:
python scripts/generate_skills_report.pySave to file:
python scripts/generate_skills_report.py --output skills_report.jsonSort by name:
python scripts/generate_skills_report.py --sort name --output sorted_skills.jsonAdd the date_added field to your SKILL.md frontmatter:
---
name: new-awesome-skill
description: "Does something awesome"
date_added: "2025-02-26"
---When onboarding many skills, use:
python scripts/manage_skill_dates.py add-missing --date 2025-02-26This adds today's date to all skills that are missing the field.
The validators now check date_added format:
# Run Python validator (strict mode)
python scripts/validate_skills.py --strict
# Run JavaScript validator
npm run validateBoth will flag invalid dates (must be YYYY-MM-DD format).
The generate_skills_report.py script produces a JSON report with statistics:
{
"generated_at": "2025-02-26T10:30:00.123456",
"total_skills": 250,
"skills_with_dates": 245,
"skills_without_dates": 5,
"coverage_percentage": 98.0,
"sorted_by": "date",
"skills": [
{
"id": "recent-skill",
"name": "recent-skill",
"description": "A newly added skill",
"date_added": "2025-02-26",
"source": "community",
"risk": "safe",
"category": "recent"
},
...
]
}Use this for:
- Dashboard displays
- Growth metrics
- Automated reports
- Analytics
Add to your pipeline:
# In pre-commit or CI pipeline
python scripts/validate_skills.py --strict
# Generate stats report
python scripts/generate_skills_report.py --output reports/skills_report.json- Use consistent format: Always use
YYYY-MM-DD - Use real dates: Reflect actual skill creation dates when possible
- Update on creation: Add the date when creating new skills
- Validate regularly: Run validators to catch format errors
- Review reports: Use generated reports to understand collection trends
Make sure the date is in YYYY-MM-DD format:
- ✅ Correct:
2024-01-15 - ❌ Wrong:
01/15/2024or2024-1-15
Make sure you're running from the project root:
cd path/to/antigravity-awesome-skills
python scripts/manage_skill_dates.py listInstall Python 3.x from python.org
- SKILL_ANATOMY.md - Complete skill structure guide
- SKILLS_UPDATE_GUIDE.md - How to update the skill collection
- EXAMPLES.md - Example skills
See CONTRIBUTING.md for contribution guidelines.