What problem does it solve? Writing SKILL.md files that Claude parses correctly requires following many subtle formatting and retrieval conventions, and mechanical rules like the description length cap or the two---- rule drift silently until a full review pass catches them. ## Core Features & Use Cases - Authoring conventions: Codifies rules for horizontal rules, bold usage, line wrapping, American spelling, description phrasing ("Use when ..."), cross-skill references, and negative instructions. - Eval-driven verdicts: Defines thresholds for keeping, improving, promoting, or discarding a skill based on measured pass-rate deltas, pass@k versus pass^k, and the Fired column. - Bundled validator: Ships scripts/check_skills.py, which checks name charset, description length, frontmatter delimiters, body length, and hard-wrapped prose across any skill tree. - Use Case: Before committing a new skill, run the validator over the repo and apply the conventions to fix a description that exceeds the 1024-character cap. ## Quick Start Review my new SKILL.md against this repo's authoring conventions and run the bundled check_skills.py validator on it.
