fuse-delta
Skill0 starsChanged 5 months agoNo licenceView on GitHub
Use this skill whenever the user wants to merge, compare, or evolve cognitive contracts, skill files, UI contracts, living documents, or constraint maps. Triggers include: "fuse these contracts", "merge these skills", "what's different between these", "absorb the delta", "combine our contracts", "sync our skill files", "one builder has X and I have Y", "evolve this contract with new learnings", or any request involving two versions of the same document where the goal is to extract resolved friction rather than simply diff text. Also triggers for Mode B (self-evolution): "update my contract with these session notes", "evolve this skill based on what we learned", "absorb this into the contract". IMPORTANT: Use this skill any time the user wants to merge knowledge between two builders, contracts, or skill instances — even if they don't use the word "fuse" or "delta".
In this repository17 other files it gives its agents.
- carousel-engineSkill
- cognitive-friction-extractorSkill
- core-extractorSkill
- crystalliseSkill
- distillSkill
- handoffSkill
- intakeSkill
- intuition-forgeSkill
- moultSkill
- occams-razorSkill
- ossifySkill
- placement-protocolSkill
- Prompt Engine Interface ContractSkill
- ruptureSkill
- spinal-columnSkill
- typographySkill
- ui-contractSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 16 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈16
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.