AB wc-decision-board
Renders the FIFA World Cup Fantasy decision board — the advisory output that surfaces 2-4 genuinely distinct, weighted options for the expert manager and ends on "your call." Takes the evolution engine's verified offspring (with fitness decomposition, genotype lineage, and specialist dissent) and formats each as an option with its concrete picks, EV/ownership-leverage/variance/progression decomposition, football reasoning, what it's betting on, the dissent, and an ownership read — then a trade-off axis, a recommended-but-overridable default tied to the rank objective, and a "what I need from you." Enforces options-not-commands, shows the working, surfaces dissent, never auto-commits. Use to present any squad/matchday/transfer/chip decision.
Renders the FIFA World Cup Fantasy decision board — the advisory output that surfaces 2-4 genuinely distinct, weighted options for the expert manager and ends…
As a process B 69/100 · Nearly there — weak spots: result and completion, when it triggers
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: 1. 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 69/100
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 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 1132 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 750: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.