This note explains how date_added support fits into the current repository structure after the apps/ and tools/ refactor.
New skills can include a date_added field in SKILL.md frontmatter:
---
name: skill-name
description: "Description"
date_added: "2026-03-06"
---
The active validators understand date_added:
tools/scripts/validate_skills.py checks the YYYY-MM-DD format.tools/scripts/generate_index.py exports date_added into skills_index.json.npm run app:setup copies the generated index to apps/web-app/public/skills.json.tools/scripts/manage_skill_dates.py manages skill dates.tools/scripts/generate_skills_report.py produces JSON reports from current skill metadata.The canonical docs for date tracking now live here:
Use those files as the source of truth instead of older root-level doc names.
# View current date coverage
python tools/scripts/manage_skill_dates.py list
# Add missing dates
python tools/scripts/manage_skill_dates.py add-missing
# Update one skill
python tools/scripts/manage_skill_dates.py update skill-name 2026-03-06
# Generate a report
python tools/scripts/generate_skills_report.py --output reports/skills_report.json
date_added is useful metadata, but the operational contributor gate remains npm run validate; strict validation is a separate hardening target for legacy cleanup.