Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →randallliuxin/gm-scaffold
Scaffold a new Godot project: project.godot + addons + base directories + e2e/conftest.py + initial git commit. Lifetime-once role — runs only on fresh projects. Explicit invocation only — use /gm-scaffold.
Passed 8 of 14 test cases with the skill, and 2 of 14 without it.
and 7 more in the full report
10 fixed2 passed either way9 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
The project folder already contains project.godot, addons/gecs/, and a non-empty git commit log. Should we run the scaffold skill again or stop and suggest the next stage?
| Checked | Without skill | With skill |
|---|---|---|
| stops scaffolding and directs to /gm-gdd | Missed | Passed |
The instructions your model reads when the skill loads.
$ARGUMENTS
You are scaffolding a brand-new Godot project. This is the lifetime-once foundation step: project.godot + addons + base directory layout + e2e/conftest.py + initial git commit. No game design happens here — that comes in /gm-gdd.
FIRST ACTION — before anything else: Write scaffold to .godotmaker/current_role.
session_start.py deletes .godotmaker/current_role on every new session
(including /clear, restart, and resume) so a stale role from a previous
session can't grant unintended write permissions. That is why every gm-*
skill re-writes its role as the first action — if a session is interrupted
mid-scaffold and you don't re-issue /gm-scaffold, write hooks will start
denying file writes silently. Re-issuing the slash command re-establishes
the role.
Read .godotmaker/stage.jsonl (treat as empty if missing) — each line is {"role": X, "ts": Y}. Find the last event in the file.
Scaffold is lifetime-once — its event gets cleared after each tag's finalize (stage.jsonl is truncated). So determine "already scaffolded" from project artifacts on disk, not the event log:
project.godot exists AND addons/gecs/ exists AND git log has at least one commit → STOP. Tell the user:
"Project is already scaffolded. Recommended next: /gm-gdd. If you need to re-scaffold (rare — usually addon migrations are handled by
tools/publish.py), just tell me."
1280x720) and rendering method.config/addon_versions.json — do not guess versions.<godot_path> --headless --import before the commit and include generated .uid files.test cases passed, vs 2 / 14 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.