agentleFS
Sign inStart free
AnmarHaniAnmarHani/SwarmVault/skills/swarm-init/SKILL.md

swarm-init

Skill5 starsChanged 4 months agoMITView on GitHub

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.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If not already set: make the vault the default for new projects?

    line 28

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

swarm-init — new project onboarding

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

Steps

  1. 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).
  2. 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 or a model name (swarm-orchestrate explains why) — but if they enable it, DO ask their plan and usage limits per platform: you cannot read those, and without them every usage number you print is invented.
    • 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.

  3. 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.

  4. 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.

  5. 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.

Influences: the original Claude Vault setup — see CREDITS.md.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free