AB skill-usage-setup
Install and set up the OpenClaw Skill Usage plugin. Use when users say: - "install skill usage" - "setup skill usage" - "add skill usage analytics" - "install leaderboard plugin" - "track which skills are used most" - "setup shared skill leaderboard" - "enable /skillusage"
As a process B 69/100 · Nearly there — 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 69/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (skill-usage-setup) differs from the folder (skill-usage)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 79 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 9 branches, has a failure section
- 100Execution cost. Instruction body is 2106 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
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
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 274: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 79 items
- +4Has examples (9 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.