SKILLEMALL.ai

BD ๐ŸŽฎ ๊ฒŒ์ž„ ๊ธฐํš ์Šคํ‚ฌ (Game Design Skill)

1. ๋ฌด๊ณผ๊ธˆ ๊ฒฝํ—˜ ์™„์ „ํ•ด์•ผ โ€” ๋ˆ ์•ˆ ์จ๋„ ๊ฒŒ์ž„ ์ฆ๊ธธ ์ˆ˜ ์žˆ์–ด์•ผ 2. ์ฒซ ์„ธ์…˜์€ ๊ด‘๊ณ  ์ตœ์†Œํ™” โ€” ๊ด€๊ณ„ ํ˜•์„ฑ ์šฐ์„  3. ๊ฐ€์น˜ ๊ตํ™˜ ๋ช…ํ™• โ€” "์ด๊ฑฐ ์‚ฌ๋ฉด ์ด๋ ‡๊ฒŒ ์ข‹์•„์ ธ์š”" 4. ๊ฒฐ์ œ ํ”„๋ ˆ์…” ๊ณผ๋„ ๊ธˆ์ง€ โ€” ํŒ์—… ํญํƒ„ โŒ 5. ๊ด‘๊ณ ๋Š” ์ž์—ฐ์Šค๋Ÿฌ์šด ์ „ํ™˜์ ์— โ€” ๊ฒŒ์ž„ํ”Œ๋ ˆ์ด ์ค‘ ์ ˆ๋Œ€ ๊ธˆ์ง€

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body โ‰ˆ 1 937 tokens Open the sourcegithub.comโ†— analyzed 2 d ago

1. ๋ฌด๊ณผ๊ธˆ ๊ฒฝํ—˜ ์™„์ „ํ•ด์•ผ โ€” ๋ˆ ์•ˆ ์จ๋„ ๊ฒŒ์ž„ ์ฆ๊ธธ ์ˆ˜ ์žˆ์–ด์•ผ 2. ์ฒซ ์„ธ์…˜์€ ๊ด‘๊ณ  ์ตœ์†Œํ™” โ€” ๊ด€๊ณ„ ํ˜•์„ฑ ์šฐ์„  3. ๊ฐ€์น˜ ๊ตํ™˜ ๋ช…ํ™• โ€” "์ด๊ฑฐ ์‚ฌ๋ฉด ์ด๋ ‡๊ฒŒ ์ข‹์•„์ ธ์š”" 4. ๊ฒฐ์ œ ํ”„๋ ˆ์…” ๊ณผ๋„ ๊ธˆ์ง€ โ€” ํŒ์—… ํญํƒ„ โŒ 5. ๊ด‘๊ณ ๋Š” ์ž์—ฐ์Šค๋Ÿฌ์šด ์ „ํ™˜์ ์— โ€” ๊ฒŒ์ž„ํ”Œ๋ ˆ์ด ์ค‘ ์ ˆ๋Œ€ ๊ธˆ์ง€

As a process D 49/100 ยท Unfinished process โ€” weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureDesigntype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
67
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters ยท all ten

How to improve

  1. Say in the description WHEN to use the skill ("use whenโ€ฆ", example requests): that is the agent's main cue.
For the model run โ€” optional
  • 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-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description 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.