swarm-eject
Skill5 starsChanged 4 months agoMITView on GitHub
Disconnect a project from SwarmVault and choose what happens to its knowledge — keep it, export it into the repo, or delete it. Use when the user wants to stop using SwarmVault here, remove the vault wiring, uninstall the framework from a project, offboard or archive a project, or delete a project's vault data.
- Deletes or force-pushes
In this repository14 other files it gives its agents.
- swarm-debugSkill
- swarm-design-deepSkill
- swarm-designSkill
- swarm-design-uiSkill
- swarm-flowSkill
- swarm-implementSkill
- swarm-initSkill
- swarm-migrateSkill
- swarm-orchestrateSkill
- swarm-reviewSkill
- swarm-skill-forgeSkill
- swarm-specSkill
- swarm-vaultSkill
- swarm-writeSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
If they say something like "remove SwarmVault from this project," that is unwire unless they explicitly say delete.
- Very specific: line 63
After unwire, swarm-flow and the phase skills no longer apply here.
≈ “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.
Files
swarm-eject — leaving cleanly
Ejecting is not rm -rf. A project is wired in six places, and a partial removal leaves the
user worse off than never installing: a marker with no registry entry, instruction files
still pointing agents at a vault that no longer has the project, hooks firing into nothing.
The eject command does the work; this skill runs the conversation.
1. Ask which exit they want
Lead with the recommendation. Most people asking this want unwire, not deletion.
| mode | what happens to the knowledge | reversible |
| unwire (default, recommend first) | stays in the vault; the project just stops being wired | yes — register brings it back |
| export | copied into the repo at docs/swarmvault-archive/, then removed from the vault | via those files |
| purge | deleted | only from the backup |
If they say something like "remove SwarmVault from this project," that is unwire unless they explicitly say delete. Ask before assuming otherwise.
2. Show the inventory before doing anything
The command's default is a dry run, so run it plainly and read the output back:
swarmvault.py eject --project <P> --mode unwire|export|purgeIt prints what leaves and what stays: note counts per vault folder, total size, the exact
instruction files and hooks to be unwired, and — for export and purge — every inbound
[[wikilink]] from other projects that would go dead. Surface the orphan warning to the
user; it is the one consequence they cannot see coming.
3. Apply
swarmvault.py eject --project <P> --mode <mode> --apply [--backup PATH]- purge asks for the project name typed back. Don't work around that prompt; if the
session is non-interactive, tell the user and let them pass
--confirm-name <P>. - A backup tarball is written outside the vault before any deletion.
--no-backupexists; don't reach for it, and never pass it on the user's behalf. - Report the printed log back rather than summarising it as "done."
Rules
- Live work blocks the eject. Open ticket claims or a running supervisor cause a refusal
listing what's holding it. Release the claims or
supervisor stopfirst, and say why — never present the refusal as a bug. - The repo is not vault property.
docs/SRS.md,docs/specs/, source, and git history are never touched at any level. If the user actually wants their SRS deleted, that's a normal file operation they ask for separately. - Global instruction files stay. They are shared with every other project; only this project's own files get unwired.
- Idempotent — a half-finished eject completes on a re-run, and
doctornames the state. - After unwire,
swarm-flowand the phase skills no longer apply here. Say so, in one line.
Undo
Unwire is reversible while the vault content is intact:
swarmvault.py register --name <P> --path <path> # then: wire --platforms <list>Export and purge are only reversible from the backup tarball. Say that out loud before applying either.
The reverse of swarm-init and FR-06's wire; the safety protocol follows the vault's
own destructive-action stance (FR-25).
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.