skill-fusionlisted
Install: claude install-skill younnieCutler/skill-fusion
# Skill Fusion
Two source skills go in. What comes out is a third capability that neither
parent could reach, executed against a real task and scored before it is kept.
**The one thing that makes this a fusion and not a pipeline:** the output must
not be reducible to "run A, then run B." A fusion transplants one skill's
*method* — its lens, its procedure, its constraints, its evaluation criteria —
into the other's *domain*. If you can describe the result as sequential
execution, the fusion failed, and the correct move is to say so and stop.
```text
Not a fusion: A fusion:
run A → feed output to B A's reasoning method
× B's subject and tools
↓ a way of working neither skill has
```
Most pairs do not fuse. Failing a summon costs the user nothing; promoting a
skill that is two skills in a trenchcoat costs them a polluted skill directory
and a tool that misleads them later.
## Scripts
Run from `scripts/`. Both are deterministic and neither improvises.
```bash
python inspect_skills.py <a> <b> # materials + relatedness screen
python inspect_skills.py --list # what is available
python inspect_skills.py --suggest -n 10 # most distant pairs, for discovery
python evaluate_fusion.py create --name N --a A --b B --operator OP --reason R
python evaluate_fusion.py evaluate --name N --scores u,n,c,r --safety pass|fail
python evaluate_fusion.py promote