
Skill Test Validator
Lints and checks other skill and agent files for structure, rubric fit and coverage
- Repository
- Donchitos/Claude-Code-Game-Studios
- Stars
- 32,965
- Licence
- MIT
- Files
- 1 file
What it does
This skill gives an agent a checklist for reviewing other skills (folders with a SKILL.md instruction file) and agents in a Claude Code project. It can lint a skill's structure against seven checks, run category rubrics, read test specs, and report which skills have specs and when they were last checked. It only reads files to judge them; it does not run the skills it reviews, so a pass means the file is well-formed, not that the skill behaves correctly.
Great for
- Maintainers of a Claude Code skill library who want consistent structure across many SKILL.md files
- Developers writing their own skills who want a quick structural check before sharing them
- Teams auditing which skills and agents have test specs and when those were last reviewed
Skip it if
- Judging whether a skill actually works for end users: the skill itself says a pass only shows the instructions cover each case, and real behaviour needs running the skill on real requests
- Projects that are not built around this studio's folder layout (studio-tests/, .claude/skills, hooks/yaml-helper.sh), since the checks assume that structure
Try asking
- “/skill-test static all”
- “/skill-test spec pitch-writer”
- “/skill-test category all”
- “/skill-test audit”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 1 original files, the MIT licence and an attribution note.
skill-test.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip skill-test.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip skill-test.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Run static on one skill first to see the output format before running static all across the library
- Treat a spec or category pass as evidence the instructions are complete, and test real requests in a throwaway copy of the project before trusting a skill
- Expect it to write files: it asks before writing in collaborative mode, but check the automation setting so writes do not happen unattended by surprise
What's inside
- SKILL.md
Redistributed unmodified from Donchitos/Claude-Code-Game-Studios under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.