validate-skills
Check skill metadata and code against official agentskills.io specs and Claude Code practices.
Install
mkdir -p .claude/skills/validate-skills && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2791" && unzip -o skill.zip -d .claude/skills/validate-skills && rm skill.zipInstalls to .claude/skills/validate-skills
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Validates skills in this repo against agentskills.io spec and Claude Code best practices. Use via /validate-skills command.Key capabilities
- →Validate skill metadata against spec
- →Check directory naming conventions
- →Verify documentation standards
- →Lint skill structure
How it works
It scans skill directories to ensure they meet agentskills.io specifications and Claude Code best practices.
Inputs & outputs
When to use validate-skills
- →Validate new skill metadata
- →Check skill for spec compliance
- →Ensure documentation standards
About this skill
Validate Skills
Validate all skills in skills/ against the agentskills.io spec and Claude Code best practices.
Validation Checklist
For each skill directory, verify:
Spec Compliance (agentskills.io)
| Check | Rule |
|---|---|
name format | 1-64 chars, lowercase alphanumeric + hyphens, no leading/trailing/consecutive hyphens |
name matches directory | Directory name must equal name field |
description length | 1-1024 characters, non-empty |
| Optional fields valid | license, metadata, compatibility if present |
Best Practices (Claude Code)
| Check | Rule |
|---|---|
| Description format | Third person, describes what + when to use |
| Body length | Under 500 lines |
| Loading is one-level deep | SKILL.md is the only progressive-disclosure entry point: every reference file must be reachable from SKILL.md. References may cross-link each other for navigation (see note below). |
| Links are markdown | Use [text](path) not bare filenames |
| No redundancy | Don't repeat description in body |
| Concise | Only add context Claude doesn't already have |
One-level-deep vs. cross-linking. The one-level-deep rule targets progressive-disclosure loading chains — a reference that can only be discovered by loading another reference first (
SKILL.md→a.md→b.md, whereb.mdis not linked fromSKILL.md). That is a defect: it hides content from the loader.It does not forbid navigational cross-links. Per AGENTS.md, reference files end with a "Related Skills" footer linking sibling references, and this is required. A cross-link is fine as long as both endpoints are also reachable directly from
SKILL.md. Only flag a reference that is reachable exclusively through another reference.
How to Run
-
Find all skill directories:
fd -t d -d 1 . skills/ -
For each skill, read
SKILL.mdand check against the rules above -
Report issues in this format:
## Validation Results ### skills/example-skill - [PASS] name format valid - [FAIL] name "example" doesn't match directory "example-skill" - [PASS] description length OK (156 chars)
References
When not to use it
- →When validating non-skill directories
- →When skipping spec compliance checks
Prerequisites
Limitations
- →Requires adherence to specific naming rules
- →Limited to agentskills.io spec
How it compares
It provides automated, spec-based validation rather than manual review of skill structure.
Compared to similar skills
validate-skills side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| validate-skills (this skill) | 2 | 6mo | Review | Beginner |
| deepwiki-rs | 25 | 9mo | Review | Intermediate |
| python-code-style | 9 | 6mo | Review | Intermediate |
| code-review-excellence | 19 | 5mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by callstackincubator
View all by callstackincubator →You might also like
deepwiki-rs
sopaco
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.
python-code-style
wshobson
Python code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.
code-review-excellence
wshobson
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
code-walk-thru
pchalasani
Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.
cookbook-audit
anthropics
Audit an Anthropic Cookbook notebook based on a rubric. Use whenever a notebook review or audit is requested.
schema-markup
davila7
When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.