skill-standardization

Run the validation script on a skill directory: Validate all skills in a directory: The script checks: The description field determines when a skill triggers. A weak description means the skill never activates; an over-broad one triggers at wrong times. Template: Principles (from agentskills.io): Before / After: Use this template as the starting point: Create evals/evals.json with 2–5 realistic test prompts: Good assertions are verifiable : file exists, JSON is valid, chart has 3 bars. Avoid vague assertions like "output is good." Output: - 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 - Required frontmatter fields ( name , description ) - name format: lowercase, no consecutive hyphens, matches directory name - description length: 1–1024 characters - allowed-tools format: space-delimited (not YAML list) - Recommended sections present - File length: warns if over 500 lines - Imperative phrasing — "Use this skill when..." not "This skill does..." - User intent, not implementation — describe what the user wants to achieve - Be explicit...