atopile-skills

To validate SKILL.md frontmatter, you check that each skill defines a required name and description field, then run repo-level verification steps to confirm all frontmatter entries remain well-formed and consistent across the project.

Keeping skill documentation invariants aligned requires a source-of-truth-first workflow where you update SKILL.md files to reflect current code, then verify that referenced paths and entrypoints match the actual repository structure and tests.

Skill docs break because path references and entrypoints in SKILL.md files become stale when code moves or files are renamed without a corresponding documentation update or invariant verification step to catch the drift.

Yes, you can enforce consistent skill documentation conventions by codifying a repo-local workflow that validates frontmatter, checks path references, and verifies invariants against the actual codebase structure for every skill entry.

No external dependencies are required to verify skill docs and frontmatter validity; the workflow operates entirely repo-local, using built-in verification steps and conventions to ensure documentation stays aligned with the source of truth.

A source-of-truth-first workflow for maintaining skill documentation means you update SKILL.md files from the actual code and tests first, then run validation steps to ensure frontmatter, paths, and invariants remain correct and reproducible.