Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →randallliuxin/gm-verify
Mechanical verification of the built game: headless build, unit tests, lint, static checks. Explicit invocation only — use /gm-verify.
Passed 7 of 13 test cases with the skill, and 4 of 13 without it.
and 5 more in the full report
8 fixed4 passed either way7 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
A linter error occurred during verification. We want to set `suggested_fallback` to `add_gdlintrc_rule`, but the linter output did not specify which rule failed (`rule_name` is null). What `suggested_fallback` value must be written in `tooling_notes`?
| Checked | Without skill | With skill |
|---|---|---|
| Emits 'escalate' as the fallback strategy when a required operand for another fallback is missing. | Missed | Passed |
The instructions your model reads when the skill loads.
$ARGUMENTS
You are performing mechanical verification of a built Godot game project. This is a non-creative, checklist-driven process.
FIRST ACTION — before anything else: Write verify to .godotmaker/current_role.
Permission: Read-only with three exceptions — you may write .godotmaker/current_role, append to .godotmaker/stage.jsonl, and write .godotmaker/verify_report.json. Verify never modifies game code or planning docs.
Read .godotmaker/stage.jsonl (treat as empty if missing) — each line is {"role": X, "ts": Y}.
role == "build" AND no event with role == "fixgap" exists anywhere in the file → STOP. Tell user to run /gm-build first.role == "verify" → STOP. Tell the user:
"Verify already ran at {timestamp} with no state-changing event since. Recommended next: /gm-evaluate. If you need to redo this step or have other plans, just tell me."
From the project root:
python tools/run_verify.py
run_verify.py wraps the four mechanical checks (build / unit tests /
lint / static check) and prints a JSON document matching Output Format
Section B to stdout. Capture stdout.
What the script does:
godot_path from .claude/godotmaker.yaml; falls back to
plain godot from PATH. A missing or broken binary surfaces as a
tooling_notes[].suggested_fallback = "escalate" entry.<godot_path> --headless --quit and writes blocking Godot diagnosticstest cases passed, vs 4 / 13 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.