skill-test

Automates validation of Claude Code Skill Units' structure and behavior via static checks, specs, rubrics, audits.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/dawn840705/claude-code-game-studios --skill skill-test-dawn840705
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-test
Source: https://github.com/dawn840705/claude-code-game-studios/tree/main/skills/skill-test
Command: npx skills add https://github.com/dawn840705/claude-code-game-studios --skill skill-test-dawn840705

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates skill files for structural compliance and behavioral correctness, ensuring every skill entry meets the repository's quality standards.

Core Features & Use Cases

  • Static validation: checks the SKILL.md frontmatter for required fields and ensures coherent structure.
  • Behavioral spec verification: cross-checks presence of test specs and catalog links to validate expected behavior.
  • Category rubrics: evaluates skills against category guidelines to ensure alignment with governance.
  • Coverage auditing: aggregates static, spec, and category results to surface gaps across the skillset.
  • Guidance and remediation: provides actionable next steps when issues are detected.

Quick Start

Run the static check for a single skill or all skills, then optionally run spec, category, or audit to review coverage.

Frequently Asked Questions about skill-test

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

FAQPage Schema
How do I validate Claude Code skill files for structural compliance?

To validate Claude Code skill files, run static checks against the SKILL.md frontmatter to ensure required fields like name, description, and allowed-tools are present and structurally coherent across the .claude/skills directory.

What is YAML frontmatter validation for skill metadata?

YAML frontmatter validation checks that SKILL.md files contain required metadata fields such as name and description, optional context, and a defined allowed-tools set to ensure quality assurance and structural compliance.

How do I audit skill coverage and behavioral correctness across a repository?

To audit skill coverage, run the audit mode which aggregates static, spec, and category validation results to surface gaps across the skillset, cross-checking test specs and catalog links to verify behavioral correctness.

Can I check skill files against category guidelines and rubrics?

Yes, you can check skill files against category rubrics by running the category mode, which evaluates skills against category guidelines to ensure alignment with governance and reports PASS, WARN, or FAIL with remediation guidance.

Do I need any external dependencies to run skill testing and validation?

No external dependencies are required to run skill testing and validation, as the tool operates directly on the repository's .claude/skills directory and requires only a SKILL.md frontmatter with name and description fields.

Why does my skill validation report a FAIL status and how do I fix it?

A FAIL status during skill validation indicates structural or behavioral non-compliance, and the tool outputs actionable remediation guidance detailing which required frontmatter fields or test specs are missing or incorrect.