validate-skills

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

3|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/ravnhq/typescript-blueprint --skill validate-skills-ravnhq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-skills
Source: https://github.com/ravnhq/typescript-blueprint/tree/main/.agents/skills/validate-skills
Command: npx skills add https://github.com/ravnhq/typescript-blueprint --skill validate-skills-ravnhq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates skills in this repository against the agentskills.io specification and Claude Code best practices.

Core Features & Use Cases

  • Verifies each skill's frontmatter for required fields (name, description) and optional metadata.
  • Ensures the directory name matches the declared skill name and enforces description length constraints.
  • Produces a structured report suitable for CI to surface non-conformant skills.

Quick Start

Run the validation tool to scan all skills and generate a report.

Frequently Asked Questions about validate-skills

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

FAQPage Schema
How do I validate skills against the agentskills.io specification in CI?

You validate skills by scanning each directory under skills/, reading SKILL.md, and enforcing frontmatter requirements like name and description to produce a structured report of deviations suitable for CI.

What frontmatter fields are required for Claude Code best practices compliance?

Required frontmatter fields for compliance include name and description, while optional metadata fields like license, metadata, and compatibility are validated if present in the SKILL.md file.

How do I lint skill directories to catch non-conformant metadata?

Linting skill directories targets each folder under skills/, checking that the directory name matches the declared skill name and enforcing description length constraints to surface non-conformant skills.

Can I run skill specification validation without external dependencies?

Skill specification validation runs without external dependencies, requiring only the skill directories containing SKILL.md files to check frontmatter fields and body quality against the spec.

What does the agentskills.io validation report include for failed skills?

The validation report includes structured results listing all deviations from the agentskills.io specification and Claude Code best practices, covering frontmatter fields, directory name mismatches, and description length violations.