This is a copy of a skill from another catalog; the rating counts the canonical one: worldsim(ClawHub)
How to improve
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
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: 58. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
warningdescription-no-when description does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 56/100
0Result and completion. Does not say what the result is
0Inputs and preconditions. Does not say what the process needs to start
0Progress reporting. Says nothing while it works
20When it triggers. No condition that starts the skill
30Running it twice. 6 mutating operations with no state check
50Failures and branches. 0 branches, has a failure section
100Tools and files. No external tools needed
100Steps. 22 steps
100Consistency. Name and required fields are in place
100Execution cost. Instruction body is 2319 tokens
medium 5 test cases, all positive: not one "should refuse" or "should ask first"
low No test case covers injection arriving through data
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
-310 of 12 scripts are never mentioned in SKILL.md
+2Single-language instructions
+3Description length 288: enough signal without eating the budget
+4Structure: 9 headings
+3Step-by-step instructions: 22 items
+4Has examples (3 code blocks)
+4Reference files are cited in the instructions (21 of 23)
+1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.
External checks
ClawHub: suspicious
This is a coherent local story-simulation skill, but it needs review because some destructive world-data operations are not protected by code-enforced confirmation or verified backups.