Swarm init

Skill AnmarHani/SwarmVault/skills/swarm-init

A shared knowledge vault + full software-engineering workflow for AI coding agents — run Claude Code and Codex in parallel with one memory, one plan.

Install

npx -y skills add AnmarHani/SwarmVault --skill swarm-init

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

19 days oldThe repository was created 19 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Start a new project connected to the SwarmVault — register it, wire platform adapters, offer git init, set vault-as-default. Use when starting a new project, connecting a project to the vault, or when the user asks to set up SwarmVault in a directory.

SKILL.md

2.8 KB, as published. Nobody here has run it

swarm-init — new project onboarding

Idempotent: safe to re-run on an initialized project (repairs missing pieces, changes nothing else).

Steps

Vault exists? swarmvault.py doctor. If no vault: offer swarmvault.py init first. Mention once: opening the vault folder in Obsidian gives the graph and backlinks — optional, never required (docs/obsidian-guide.md).
Ask (only what is genuinely the user's):
- Project name (default: directory name).
- Isolation: shared (cross-project queries see it) or isolated?
- Which agentic platforms to wire — the tools they actually have (claude-code, codex, gemini, opencode, droid, cursor, copilot, amp, or any other agent CLI by name), and global or per-project.
- Git init, if no repo (recommended — the flow's traceability uses commits; optional).
- Optional orchestration for this project? Ask it as a pace — off / budget / balanced / fast — plus whether workers may edit code. Never ask for a worker count, a usage limit, or a model name (swarm-orchestrate explains why).
- If not already set: make the vault the default for new projects? → save "auto_init_new_projects": true in ~/.swarmvault.json; future inits skip the ceremony.
Do it in one command — it registers, wires every named platform's own instruction file (plus Claude Code skills and hooks), syncs, and verifies:
```
swarmvault.py setup --platforms <list> --scope global|project \
  [--name <name>] [--isolated] [--autonomy off|budget|balanced|fast] [--read-only]
```
Already-registered project, or only need part of it? register / wire --platforms … / sync --quiet / doctor are the same steps individually. Never leave the user manual file edits.
Disclaimer (show once, verbatim):

SwarmVault stores project knowledge as plain files and runs local scripts. Auditing your environment, installed packages, and the data you place in the vault is your responsibility. Isolation flags are cooperative filtering between agents, not a security boundary.
Point forward: /swarm-flow starts the SDLC (first stop: swarm-spec).

Edge cases

Directory inside an already-registered project → warn (nested projects) and require explicit confirmation.
Name collision → register refuses; pick another name.
Existing marker with a different name → repair with register --repair or honor the marker; never two names for one directory.