BD ๐ฎ ๊ฒ์ ๊ธฐํ ์คํฌ (Game Design Skill)
1. ๋ฌด๊ณผ๊ธ ๊ฒฝํ ์์ ํด์ผ โ ๋ ์ ์จ๋ ๊ฒ์ ์ฆ๊ธธ ์ ์์ด์ผ 2. ์ฒซ ์ธ์ ์ ๊ด๊ณ ์ต์ํ โ ๊ด๊ณ ํ์ฑ ์ฐ์ 3. ๊ฐ์น ๊ตํ ๋ช ํ โ "์ด๊ฑฐ ์ฌ๋ฉด ์ด๋ ๊ฒ ์ข์์ ธ์" 4. ๊ฒฐ์ ํ๋ ์ ๊ณผ๋ ๊ธ์ง โ ํ์ ํญํ โ 5. ๊ด๊ณ ๋ ์์ฐ์ค๋ฌ์ด ์ ํ์ ์ โ ๊ฒ์ํ๋ ์ด ์ค ์ ๋ ๊ธ์ง
1. ๋ฌด๊ณผ๊ธ ๊ฒฝํ ์์ ํด์ผ โ ๋ ์ ์จ๋ ๊ฒ์ ์ฆ๊ธธ ์ ์์ด์ผ 2. ์ฒซ ์ธ์ ์ ๊ด๊ณ ์ต์ํ โ ๊ด๊ณ ํ์ฑ ์ฐ์ 3. ๊ฐ์น ๊ตํ ๋ช ํ โ "์ด๊ฑฐ ์ฌ๋ฉด ์ด๋ ๊ฒ ์ข์์ ธ์" 4. ๊ฒฐ์ ํ๋ ์ ๊ณผ๋ ๊ธ์ง โ ํ์ ํญํ โ 5. ๊ด๊ณ ๋ ์์ฐ์ค๋ฌ์ด ์ ํ์ ์ โ ๊ฒ์ํ๋ ์ด ์ค ์ ๋ ๊ธ์ง
As a process D 49/100 ยท Unfinished process โ weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use whenโฆ", example requests): that is the agent's main cue.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 49/100
- 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
- 40Consistency. Frontmatter name (๐ฎ ๊ฒ์ ๊ธฐํ ์คํฌ (Game Design Skill)) differs from the folder (game-design)
- 100Tools and files. No external tools needed
- 100Steps. 40 steps
- 100Execution cost. Instruction body is 1937 tokens
- 100Running it twice. No mutating operations
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 153: enough signal without eating the budget
- +4Structure: 40 headings
- +3Step-by-step instructions: 40 items
- +4Has examples (22 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.