Start using .uniloom
A project without .uniloom/ offers Start using .uniloom at the top of its Toolkit tab: "Write each skill once, for every agent." With .uniloom/, each skill is kept once and published to every agent you pick.
Press it, and Uniloom first says what it will do:
- create
.uniloom/config.toml, listing the agents and every skill; - move each skill from the agents' own folders, such as
.claude/skillsand.agents/skills, into.uniloom/skills/, and link each agent's folder back to it. Where two agents keep different copies, you pick which one stays; - make the instructions one file:
- with neither file, it creates
AGENTS.md, the instructions every agent reads; - with
AGENTS.mdand aCLAUDE.mdof its own, it addsCLAUDE.md's text to the end ofAGENTS.mdand makesCLAUDE.mda link to it; - with only
CLAUDE.md, that stays the real file andAGENTS.mdbecomes the link; - leave each MCP server where it is, in its agent's own file.
Under Publish to, pick the agents.
What it protects#
- Nothing is committed. Projects → Code → Changes shows every file, and Discard brings any of them back.
- A copy before removing. Before it removes a skill folder or a
CLAUDE.mdthat git does not track, Uniloom copies it touniloom-adopt/in the project's git folder. That copy is never committed. - Nothing outside the project. A link inside a skill folder is skipped and listed, never followed, so a file such as a key in
~/.sshis never copied in. A skill whose folder is outside the project is not moved, and a.uniloomthat is a link is refused. - Links become files first. An
AGENTS.mdthat is a link becomes a real file with the same text.
Last updated