AC defold
Defold game engine development. Triggers: "Defold", "Defold project", "Defold engine", "Lua game", "mobile game development", "build a game", "game engine", "create game", "sprite animation", "physics collision", "game save system". Covers: GO/components/message passing, GUI/Druid, physics/collision/forces, animation/flipbook/Spine, input/binding, Factory/CollectionProxy, DefSave, game patterns. Use for any Defold-based game project.
As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
How to improve
- 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: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Defold game engine development. Triggers: "Defold", "Defold projec… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 61/100
- 0Result and completion. Does not say what the result is
- 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
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 659 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 11 example trigger phrases
- +3Description length 437: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (9 code blocks)
- +4Reference files are cited in the instructions (8 of 8)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.