claude-skill-spec-audit

Validate SKILL.md frontmatter against the agentskills.io specification.

15|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/jackchuka/skills --skill claude-skill-spec-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-skill-spec-audit
Source: https://github.com/jackchuka/skills/tree/main/claude-skill-spec-audit
Command: npx skills add https://github.com/jackchuka/skills --skill claude-skill-spec-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates auditing of installed skills to ensure all SKILL.md frontmatter adheres to the agentskills.io specification, preventing gaps in metadata and naming standards.

Core Features & Use Cases

  • Validates required frontmatter fields (name, description) and optional metadata (compatibility, metadata, argument-hint).
  • Checks naming conventions, scope prefixes, platform prefixes, and allowed abbreviations to ensure consistency across skills.
  • Generates a compliance report and offers automated fixes with the --fix option.

Quick Start

Run claude-skill-spec-audit to scan your installed skills for spec compliance and report missing or misaligned fields.

Frequently Asked Questions about claude-skill-spec-audit

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

FAQPage Schema
How do I validate SKILL.md frontmatter against the agentskills.io spec?

To validate SKILL.md frontmatter, run the claude-skill-spec-audit tool to scan installed skills and report missing or misaligned fields like name, description, and metadata for compliance.

What frontmatter fields are required for skills to be compliant?

Required frontmatter fields for spec compliance include name and description, while optional metadata fields cover compatibility, metadata, and argument-hint to ensure full agentskills.io spec validation.

Can I automatically fix missing metadata in my installed skills?

Yes, you can automatically fix missing metadata by running the audit with the --fix option, which corrects frontmatter gaps and naming convention errors for compliant skills.

How do I check naming conventions and scope prefixes for skill compliance?

You check naming conventions and scope prefixes by auditing installed skills, which scans SKILL.md files to verify platform prefixes, scope prefixes, and allowed abbreviations against the specification.

Does the skill audit support filtering by specific skill names?

Yes, the audit supports filtering by skill name, allowing you to scan a specific installed skill instead of the entire local environment to generate a targeted compliance report.

What happens when a skill audit detects non-compliant frontmatter?

When a skill audit detects non-compliant frontmatter, it generates a compliance report detailing missing or misaligned fields, and optionally applies automated fixes via the --fix option.