skill-standardization

# Skill Standardization ## When to use this skill - Creating a new SKILL.md file from scratch - Auditing existing skills for Agent Skills specification compliance - Converting legacy skill formats (non-standard headings, frontmatter) to standard - Improving skill descriptions to trigger more reliably on relevant prompts - Adding evaluation test cases (`evals/evals.json`) to a skill - Batch-validating all skills in a directory for consistency ## Agent Skills Specification Reference ### Frontmatter fields | Field | Required | Constraints | |-------|----------|-------------| | `name` | Yes | 1–64 chars, lowercase alphanumeric + hyphens, no leading/trailing/consecutive hyphens, must match parent directory name | | `description` | Yes | 1–1024 chars, must describe what skill does AND when to trigger | | `allowed-tools` | No | Space-delimited list of pre-approved tools | | `compatibility` | No | Max 500 chars, environment requirements | | `license` | No | License name or reference to bundled file | | `metadata` | No | Arbitrary key-value map for additional fields | ### Standard directory structure ``` skill-name/ ├── SKILL.md # Required ├── scripts/ # Optional: executable scripts ├── references/ # Optional: detailed documentation ├── assets/ # Optional: templates, images, data └── evals/ # Optional: evaluation test cases └── evals.json ``` ### Progressive disclosure tiers | Tier | What's loaded | When | Token budget | |-----...