Consolidate the repository into clearer apps, tools, and layered docs areas so contributors can navigate and maintain it more reliably. Align validation, metadata sync, and CI around the same canonical workflow to reduce drift across local checks and GitHub Actions.
2.0 KiB
2.0 KiB
Date Tracking Implementation Summary
This note explains how date_added support fits into the current repository structure after the apps/ and tools/ refactor.
What Exists Today
Frontmatter support
New skills can include a date_added field in SKILL.md frontmatter:
---
name: skill-name
description: "Description"
date_added: "2026-03-06"
---
Validator support
The active validators understand date_added:
tools/scripts/validate_skills.pychecks theYYYY-MM-DDformat.- Supporting JS validation/test helpers are aware of the field where relevant.
Index and web app support
tools/scripts/generate_index.pyexportsdate_addedintoskills_index.json.npm run app:setupcopies the generated index toapps/web-app/public/skills.json.- The web app can render the field anywhere the UI surfaces it.
Maintenance scripts
tools/scripts/manage_skill_dates.pymanages skill dates.tools/scripts/generate_skills_report.pyproduces JSON reports from current skill metadata.
Canonical Documentation
The canonical docs for date tracking now live here:
Use those files as the source of truth instead of older root-level doc names.
Common Commands
# 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
Notes
- Repository-wide coverage can change over time as new community skills are added, so this document avoids hardcoding counts.
date_addedis useful metadata, but the operational contributor gate remainsnpm run validate; strict validation is a separate hardening target for legacy cleanup.