BC wc-building-block-crossover
The recombination operator for the FIFA World Cup Fantasy evolution engine. Crosses elite candidate squads/plans at BUILDING-BLOCK boundaries (Captain Core, Clean-Sheet Spine, Mid-Engine, Differential Pod, Enabler Bench; or for matchday plans the XI/captain-ladder/bench/sub/chip blocks) — harvesting the strongest module from each parent rather than swapping individual players — then runs a feasibility REPAIR operator (budget, nation cap, formation, 15-man shape) that restores legality from the cheapest block first and never guts a value-bearing block. Records block lineage (which parent each block came from). Implements the Evolution document's central lesson that naive crossover destroys good building blocks. Use in the recombine stage after fitness selection.
The recombination operator for the FIFA World Cup Fantasy evolution engine.
As a process C 60/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
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 60/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1195 tokens
- 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
- +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 771: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.