Support.

Silo Skills is sandboxed and starts with access to no folders at all, so it opens on a small read-only sample until you grant access. Press Select Home Folder… in the banner and choose the folder named after your macOS user, not a subfolder. Agents keep their configuration in hidden folders directly inside the home folder, so any other choice is refused and the banner says so. The grant is stored as a security-scoped bookmark and survives relaunch, so you only do this once.

Eight coding agents, each by its standard configuration folders inside your home folder. The Agents list in the sidebar names all eight and shows how many assets it found for each. Silo Skills only reads and writes inside the home folder you granted, and only in those agent folders.

If the agent was installed or set up after the last scan, press Refresh in the toolbar or ⌘R. An agent that keeps everything inside a project folder rather than in your home folder has nothing for Silo Skills to find, because it never looks inside your projects.

That agent has nowhere Silo Skills can put an MCP server. Servers are read from, and copied into, the JSON settings file each agent loads. Of the eight agents, one keeps its servers in a TOML file that Silo Skills neither reads nor edits, and another has no MCP file at all, so both show a dash instead of offering a copy the agent would never use. Point at the dash to see the reason.

Neither, until you choose. Diverging means agents hold an asset with the same name but different contents; Show Diverging Only hides the sets whose copies match. Silo Skills shows you both and changes nothing on its own. If you want one version everywhere, press Broadcast Version on that copy: it overwrites each other copy where it lives, after taking a snapshot of each.

The Fleet Optimizer starts at 100 and takes points off for empty stubs and for skills with no header. It also lists skills with no description and legacy drafts. A skill copied into several agents is never counted as a problem, because each agent reads only its own folder. Legacy drafts are never changed automatically; Inspect opens them for you to review.

Yes, if the copy replaced something. Every edit, deletion, copy and optimizer fix takes a snapshot of what it replaces before writing, and if the snapshot cannot be written the change is refused. Open Snapshots & Safety, select the entry from before the change, and press Restore…. The current version is saved as a new snapshot first, so the restore can be undone too. A copy that landed where nothing existed before can simply be deleted, and that deletion is snapshotted as well.

In a hidden folder in your home, .silo-skills/backups. Reveal in Finder in Snapshots & Safety opens it, and Delete removes one snapshot from the archive for good. Removing the app does not remove that folder; delete it yourself if you want every snapshot gone.

No. Silo Skills ships with no network entitlement at all, so it cannot reach the network even in principle. There is no account, no sync service, and no telemetry.

No. Reading happens on every scan; writing never happens on its own. Copies, edits, fixes and deletions run only when you start them, and a snapshot of anything they replace comes first. Creating a skill or MCP server with a name that is already taken is refused rather than overwriting the existing one.