skill-test

Validate SKILL.md frontmatter and structure across .claude/skills.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/brand6/Claude-Code-Game-Studios-zh-auto --skill skill-test-brand6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-test
Source: https://github.com/brand6/Claude-Code-Game-Studios-zh-auto/tree/main/.claude/skills/skill-test
Command: npx skills add https://github.com/brand6/Claude-Code-Game-Studios-zh-auto --skill skill-test-brand6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates the structural and behavioral correctness of all skills under .claude/skills by performing static checks, spec validations, and audit reporting.

Core Features & Use Cases

  • Verifies that every skill's SKILL.md frontmatter includes required fields (name, description, argument-hint, user-invocable, allowed-tools).
  • Checks multi-phase structure, proper keyword usage, and collaboration guidance.
  • Generates comprehensive checks and audit-ready reports for skills across static, spec, category, and audit modes.

Quick Start

Run /skill-test static [name] to validate a single skill, or /skill-test static all to validate every skill.

Frequently Asked Questions about skill-test

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

FAQPage Schema
How do I validate skill structure and frontmatter in markdown files?

Skill structure validation parses SKILL.md frontmatter to verify required fields like name, description, argument-hint, user-invocable, and allowed-tools. It executes static checks on markdown files to confirm structural correctness and specification compliance across all defined skill units.

What is spec verification for skill definitions and when do I need it?

Spec verification checks multi-phase structure, proper keyword usage, and collaboration guidance within skill definitions. You need spec verification when auditing skills to ensure behavioral correctness and that phase headings, exit guidance, and collaboration prompts meet required specifications.

Can I run a static check on all skills at once or do I validate them individually?

You can validate all skills at once by running the static all command, or validate a single skill by specifying its name. Both methods generate audit-ready reports covering frontmatter fields, keywords, and structural sections across static and audit modes.

What's the best way to audit skill correctness across different validation modes?

Auditing skill correctness involves running static, spec, category, and audit modes to evaluate structural and behavioral integrity. This multi-mode approach identifies missing frontmatter fields, verifies phase headings, and generates comprehensive audit reports for every skill unit under the skills directory.

Does skill testing check for required sections and collaboration prompts in the markdown body?

Skill testing verifies that the markdown body contains required sections and guidance by checking for phase headings, keywords, collaboration prompts, and exit guidance. It ensures every skill unit includes the necessary structural components alongside valid frontmatter fields.