skill-test

/skill-test — Validate a Summer Skill

Three modes. Pick by the user's intent.

Mode: static — Structural lint (default for "test this skill")

For a single skill at skills/<category>/<name>/, run these checks:

1. Frontmatter completeness. name, description, license, compatibility, category present. name matches the directory name.
2. SKILL.md length. ≤ 500 lines. (Progressive disclosure rule from Anthropic spec.)
3. MCP-preferred + file-edit-fallback. If the skill mutates scenes or resources, body must show both:
   • At least one summer_* MCP tool example.
   • At least one file-edit fallback block (e.g., raw .tscn snippet) OR an explicit "no fallback for this — Summer MCP required" note.
4. Collaborative protocol. If the skill triggers user-visible writes, body must contain at least one of: May I, I'm about to, Continue?, OK?, Proceed?. Skills that only inspect/read are exempt.
5. Template-id resolved. If the skill's frontmatter declares template-id: <id>, that id must exist in references/template-registry.md.
6. Tests/spec.md present. Every skill in a non-_meta category must have tests/spec.md with at least one ## Case heading.
7. Relative links resolve. Every ](../references/...), ](../../references/...), ](./references/...), and ](./examples/...) link must point at an existing file (FAIL if broken). Forward references in ## See also to other SKILL.md files (e.g., [design-mechanic](../../gameplay-mechanics/design-mechanic/SKILL.md)) are allowed to dangle and only WARN if the target is missing — the catalog evolves and skills should be free to point at planned skills.

Output:

skill: <category>/<name>
  PASS  (1) frontmatter complete
  PASS  (2) length 217 / 500 lines
  FAIL  (3) no MCP-preferred example found in body
  PASS  (4) collaborative protocol present
  PASS  (5) template-id resolved
  PASS  (6) tests/spec.md exists
  PASS  (7) all relative links resolve

6 PASS / 1 FAIL — fix item 3 before commit.

Mode: spec — Behavioral spec runner

For a single skill, read both skills/<category>/<name>/SKILL.md and tests/specs/<name>.md. For each ## Case in the spec:

1. Lay out the Fixture (starting state, available tools).
2. Read the Input (user prompt).
3. Reason: given the skill's instructions and this fixture, would the agent follow the Expected MCP tool sequence?
4. For each assertion under **Assertions:**, mark [x] if the skill's instructions would satisfy it, [ ] if not, with a one-line reason.

Output: an annotated copy of the spec with assertions filled in, plus a pass-rate.

No code execution. Pure reasoning over text.

Mode: audit — Whole library report

Read the skills: array in .claude-plugin/plugin.json. For each registered skill:

1. Run static mode on the skill.
2. Note any last-tested: field in the SKILL.md frontmatter (optional).
3. Flag skills failing static checks.

Output: a table with PASS / FAIL counts and a punch list of skills needing attention.

When to use which mode

User said	Mode
"test the fps-controller skill"	static
"lint this skill"	static
"does this skill actually do what it should?"	spec
"run the behavioral check"	spec
"audit the skill library"	audit
"what skills need work"	audit

Collaborative protocol

This skill is read-only. It never writes. No "May I" needed.

See also

• references/collaborative-protocol.md
• references/template-registry.md
• tests/runner.md
• tests/specs/ — per-skill behavioral specs