Silo Skills.
Your coding agents’ configuration, side by side.
Each coding agent keeps its skills, rules and MCP servers in its own hidden folder. A skill gets copied into several of them and then edited in only one; a server is wired into one agent and missing from the next. Silo Skills reads eight of those layouts and shows you which copies still match.
A blank cell is a missing wiring.
Skills and MCP servers run down the side, agents across the top. A blank cell means one agent lacks something another agent has, and one click copies it across. Where an agent has nowhere to put that kind of asset, the cell shows a dash and says why when you point at it. MCP servers are read from the JSON settings file each agent actually loads, and an agent that keeps them in another format is marked as not managed instead of looking empty.
Which copy is the real one.
Duplicates & Parity gathers copies that share a name across agents and sorts them into identical sets and sets that have drifted apart, so you can see where two agents disagree about the same skill. Pick the version you trust and Broadcast Version writes it over each other copy in its own place, after a snapshot of each. Nothing is merged or chosen for you.
Snapshot first, or not at all.
Every edit, deletion, copy and optimizer fix saves a snapshot of what it replaces before writing. If that snapshot cannot be saved, the change is refused. Snapshots & Safety previews each one and puts it back at the path it came from, saving the current version first so a restore can be undone too.
Skills, rules and prompts, slash commands, plugins, MCP servers and settings files from every agent it finds, in one searchable list. Filter by agent, by type, or by area such as design, testing and deployment.
Scores your setup out of 100 and finds empty stubs, skills with no header or description, and legacy drafts. Stubs and missing headers are fixed in one click or one at a time. A skill shared by several agents is never counted as clutter, and drafts wait for you to decide.
Create a skill, rule or MCP server for an agent, and edit skills, rules and server entries where they live. A skill or server name that is already taken is refused, not overwritten. Editing a server keeps the fields the form does not show, such as its address and headers.
Send skills, MCP servers, rules and slash commands from one agent to any others that have a place for them, one item or a batch at a time. Plugins and settings files stay with the agent that owns them.
Until you grant your home folder, the workspace runs on a small built-in sample fleet, so you can see the matrix, the drift report and the optimizer at work first. The sample lives in memory and nothing in it can be changed.
Silo Skills asks once for your home folder through the standard macOS panel, and any other folder is refused. Inside it, Silo Skills reads the agent folders and settings files and never opens your projects' source code. Snapshots stay in a folder in your home.