validate-skills

Validates skill directories against the agentskills.io specification and Claude Code best practices.

3|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/firstsun-dev/skills --skill validate-skills-firstsun-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate-skills
Source: https://github.com/firstsun-dev/skills/tree/main/plugins/agent-toolkit/skills/validate-skills
Command: npx skills add https://github.com/firstsun-dev/skills --skill validate-skills-firstsun-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Skill authors often ship directories with malformed frontmatter, mismatched names, or broken progressive-disclosure structures that prevent agents from discovering and loading skills correctly. This Skill audits every skill directory in a repository against the agentskills.io spec and Claude Code authoring guidelines so defects are caught before publication. ## Core Features & Use Cases - Spec Compliance Checks: Verifies name format (1-64 chars, lowercase alphanumeric with hyphens), name-to-directory matching, description length (1-1024 chars), and validity of optional fields like license and metadata. - Best Practice Linting: Enforces third-person descriptions, body length under 500 lines, one-level-deep reference loading, markdown link formatting, and conciseness rules. - Structured Reporting: Produces per-skill PASS/FAIL results in a consistent report format. - Use Case: Before publishing a new skill to a shared repository, run the validation to confirm the SKILL.md frontmatter matches its directory name and that every reference file is reachable directly from SKILL.md. ## Quick Start Ask the agent to run /validate-skills to audit all skill directories in the skills folder and report any spec or best-practice violations.

Frequently Asked Questions about validate-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a Claude Code skill against the agentskills.io spec?▼

Run the /validate-skills command to audit each skill directory. It checks name format, name-to-directory matching, description length, and optional field validity, then reports PASS/FAIL results per skill.

What naming rules apply to skill directories and SKILL.md frontmatter?▼

The name must be 1-64 characters of lowercase alphanumeric characters and hyphens, with no leading, trailing, or consecutive hyphens. The directory name must exactly equal the name field in the frontmatter.

What is the one-level-deep rule for skill reference files?▼

Every reference file must be reachable directly from SKILL.md so the loader can discover it. Navigational cross-links between references are allowed, but a reference reachable only through another reference is flagged as a defect.

Why does skill validation fail on description fields?▼

Descriptions fail when they are empty, exceed 1024 characters, are not written in third person, or fail to describe what the skill does and when to use it. The body should also avoid repeating the description.

What are the limitations of this skill validation approach?▼

Validation is checklist-based and covers structural and authoring rules only. It does not execute scripts, verify runtime behavior of a skill, or test whether instructions produce correct agent output.