Agent skill · writing content · aiskillstore

skill-standardization

Standardize and validate SKILL.md files against the Agent Skills specification (agentskills.io). Use when creating new skills, auditing existing skills for spec compliance, converting legacy skill formats to standard structure, or improving descriptions for reliable triggering. Triggers on: "validate skill", "create SKILL.md", "standardize skill format", "check skill spec", "skill frontmatter", "improve skill description", "add evals to skill".

Why this skill is useful

Adds a validation script for standardizing SKILL.md files, ensuring compliance with the Agent Skills specification.

What it needs

Requires bash installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.

What this skill does

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 Progressive disclosure tiers Tier What's loaded When Token budget ------ -------------- ------ ------------- 1. Catalog name + description Session start ~100 tokens per skill 2. Instructions Full SKILL.md body On activation < 5000 tokens (500 lines max) 3. Resources scripts/, references/ When needed Varies Instructions Step 1: Validate an existing skill Run the validation script on a skill directory: Validate all skills in a directory: The script checks: 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 Step 2: Write an effective description 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): 1. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills aiskillstore/skill-standardization

View the source on GitHub

Browse the @skills marketplace