SKILLEMALL.ai
GitHub ↗ RU Sign in

CB skill-test

Validate skill files for structural compliance and behavioral correctness. Four modes: static linter, spec, category rubric, audit.

Donchitos/Claude-Code-Game-Studios Claude Code author: Donchitos MIT 1 file body ≈ 7 000 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Validate skill files for structural compliance and behavioral correctness.

As a process B 69/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, progress reporting

AnalyzerData and analyticsAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
85/100
safety, quality, tests
Safety 60%
99
Quality 40%
65
Run on models
none yet
Process rating
B
69/100
Nearly there
Progress reporting w 2
0
When it triggers w 12
20
Inputs and preconditions w 11
30
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 1

✓ No critical or high findings

Medium and low: 1
  • low Broad scope meta-dynamic-shell SKILL.md:10
    Shell command executed automatically when the skill loads (Claude Code !`cmd` preamble)
    !`bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation`

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 7000 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 69/100

  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 55Failures and branches. 1 branches
  • 60Result and completion. Output format stated, no completion criterion
  • 70Execution cost. Instruction body is 7000 tokens
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 62 steps
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +1No license
  • +2Single-language instructions
  • +3Description length 131: enough signal without eating the budget
  • +4Structure: 33 headings
  • +3Step-by-step instructions: 62 items
  • +3Output format is stated explicitly
  • +4Has examples (6 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.