AC kitchen-war-rts
Delivers and maintains 厨房战争原型 (Kitchen War), a single-file HTML5 Canvas real-time strategy game built in the style of Red Alert (红警) — base building, resource harvesting, unit production, tech tree, fog of war, box-select plus group commands, an attacking enemy AI, a superweapon, and win/lose by destroying the enemy's central kitchen. Use this skill when the user asks for a Red Alert-style web RTS, a playable browser strategy game, 做一个红色警戒那样的游戏, 帮我做个能玩的战略游戏, or wants to create/extend/fix the Kitchen War game. The bundled index.html is self-contained with no external dependencies and opens directly in any browser.
Delivers and maintains 厨房战争原型 (Kitchen War), a single-file HTML5 Canvas real-time strategy game built in the style of Red Alert (红警) — base building, resource…
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 57/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 7 mutating operations with no state check
- 40Consistency. Frontmatter name (kitchen-war-rts) differs from the folder (war-skill)
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 48 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 2337 tokens
- 100Progress reporting. Reports progress
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 620: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 48 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.