agentleFS
ImtylerrrrrrImtylerrrrrr/second-brain/skills/setup/SKILL.md

setup

Skill1 starsChanged 5 months agoMITView on GitHub

One-time setup of a second-brain vault — scaffolds Projects/, registers the vault for auto-sync, merges usage rules into CLAUDE.md. Use when the user wants to set up second-brain in a folder containing their git repos.

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-voice-transcription, add-discord and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • juancruzmunozalbeloSkill

    add-voice-transcription

    Add voice message transcription to NanoClaw using OpenAI's Whisper API. Automatically transcribes WhatsApp voice notes so the agent can read and respond to them.

    Also in 5 projects that use this

  • MicrosoftSkill

    add-discord

    Add Discord bot channel integration via Chat SDK.

    Also in 11 projects that use this

  • MicrosoftSkill

    add-slack

    Add Slack channel integration via Chat SDK.

    Also in 11 projects that use this

  • juancruzmunozalbeloSkill

    add-telegram-swarm

    Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".

    Also in 7 projects that use this

  • +8 more from microsoft

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Merge the CLAUDE.md block: Read ${CLAUDE_PLUGIN_ROOT}/templates/CLAUDE-block.md.

    line 27
  2. Distinctive:

    No bash available (Windows without WSL/git-bash) → explain the requirement and stop before step 3.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 168 edited versions of this file we could read. “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

second-brain: setup

One-time onboarding of a vault (a folder containing the user's git repos). All operations are idempotent; never overwrite an existing user file.

Steps

  1. Locate the vault root. Default candidate: the current working directory. Count git repos directly under it (ls -d */.git 2>/dev/null | wc -l). Present the candidate path + repo count and ask the user to confirm or supply a different absolute path. 0 repos → warn ("no git repos found here — sync will produce an empty board") but proceed if confirmed.
  2. Scaffold Projects/ — copy each template only if the destination does not exist:
    • ${CLAUDE_PLUGIN_ROOT}/templates/Projects/Dashboard.md → <vault>/Projects/Dashboard.md
    • ${CLAUDE_PLUGIN_ROOT}/templates/Projects/_PROTOCOL.md → <vault>/Projects/_PROTOCOL.md
    • ${CLAUDE_PLUGIN_ROOT}/templates/Projects/_TEMPLATE.md → <vault>/Projects/_TEMPLATE.md
  3. Register the vault (idempotent):
    mkdir -p ~/.claude/second-brain && touch ~/.claude/second-brain/vaults
    grep -qxF "<abs-vault-path>" ~/.claude/second-brain/vaults || echo "<abs-vault-path>" >> ~/.claude/second-brain/vaults
  4. First sync: bash "${CLAUDE_PLUGIN_ROOT}/scripts/sync.sh" — then read <vault>/Projects/_AUTO_status.md and report which repos were found and which stubs were created.
  5. Merge the CLAUDE.md block. Read ${CLAUDE_PLUGIN_ROOT}/templates/CLAUDE-block.md. In <vault>/CLAUDE.md:
    • file absent → create it containing exactly the block;
    • file present without <!-- second-brain:start --> → append the block at the end;
    • markers present → replace everything between <!-- second-brain:start --> and <!-- second-brain:end --> with the current block (idempotent re-run).
  6. Summarize: vault path, repos found, stubs created, note that the plugin's Stop hook now refreshes git facts automatically (best-effort), and next steps — /second-brain:start-session to begin; /second-brain:analyze <repo> to onboard notes properly.

Rules

  • Idempotent everywhere; never clobber user content.
  • No bash available (Windows without WSL/git-bash) → explain the requirement and stop before step 3.

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.