AB yoooclaw-world-cup-match-talk-scene-en
Use to generate World Cup football conversation kits from standardized match input and notification retrieval. It supports prep for fan-group chats, in-person viewing, social posts, or selected modules such as "understand the match in 30 seconds," "main match highlights," "what everyone is discussing," "expert-sounding match lines," and "generate a Moments post." It can retrieve Chinese public sports sources and, when notifications or fan groups are relevant, use `openclaw ntf search` to extract matching mobile-notification signals.
Use to generate World Cup football conversation kits from standardized match input and notification retrieval.
As a process B 67/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting
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: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 67/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Failures and branches. 4 branches
- 85Steps. 71 steps, 3 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3765 tokens
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)
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 538: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 71 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 99.