BF game-dev-gdd
Guided Game Design Document writing using structured templates. Walks through each section of a GDD with system decomposition, mechanics breakdown, and narrative design. Produces a complete, navigable design document.
Guided Game Design Document writing using structured templates.
As a process F 30/100 · Will not run — References files that are not bundled: 01-overview.md, 02-mechanics.md, 03-systems.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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 · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: 01-overview.md - warning
missing-refreference to a missing file: 02-mechanics.md - warning
missing-refreference to a missing file: 03-systems.md - warning
missing-refreference to a missing file: 04-levels.md - warning
missing-refreference to a missing file: 05-narrative.md - warning
missing-refreference to a missing file: 06-ui-ux.md - warning
missing-refreference to a missing file: 07-audio.md - warning
missing-refreference to a missing file: 08-content.md - warning
missing-refreference to a missing file: 09-monetization.md - warning
missing-refreference to a missing file: 10-tech-spec.md - note
frontmatter-keyunknown frontmatter key "triggers"
Process rating: all ten parameters 30/100
- 0Tools and files. 10 referenced file(s) missing: 01-overview.md, 02-mechanics.md, 03-systems.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 85Steps. 7 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2253 tokens
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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 217: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.