agentleFS
yuelenghanyuelenghan/brain-vault/.agents/skills/setup-brain/SKILL.md

setup-brain

Skill1 starsChanged 3 months agoMITView on GitHub

Initialize the brain-vault shared identity layer and optional organize capabilities for Codex sessions by following the canonical `.claude/skills/setup-brain/SKILL.md`. Triggers: setup brain, initialize brain-vault, 初始化 brain-vault, 补全身份层, 安装工具.

4 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

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Follow that canonical file strictly.

    line 13
  2. Very specific:

    If .claude/skills/setup-brain/SKILL.md does not exist, stop and say the vault is missing the canonical brain-vault setup skill, so setup …

    line 14
  3. Distinctive:

    Do not delete user files; confirm before running install commands, overwriting existing config, committing to git, or scheduling tasks.

    line 15
  4. Very specific:

    Treat CLAUDE.md as the vault's shared identity layer.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 4 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

Setup Brain for Codex sessions

This is the Codex-session entry point for brain-vault setup. The working directory must be the vault root.

Execution rules

  1. First read .claude/skills/setup-brain/SKILL.md; it is the canonical workflow for initializing the shared identity layer and optional organize capabilities.
  2. Follow that canonical file strictly. If this file conflicts with .claude/skills/setup-brain/SKILL.md, the .claude file wins.
  3. If .claude/skills/setup-brain/SKILL.md does not exist, stop and say the vault is missing the canonical brain-vault setup skill, so setup cannot be run safely.
  4. Do not delete user files; confirm before running install commands, overwriting existing config, committing to git, or scheduling tasks.
  5. Treat CLAUDE.md as the vault's shared identity layer. When Codex needs the user's long-term identity, goals, current projects, or collaboration preferences, read ## Who I am, ## This year's goals, ## Collaboration preferences, and ## Current projects there. AGENTS.md is a symlink to CLAUDE.md; never edit it directly.
  6. For Codex CLI / Copilot CLI support, only update project-local instruction or skill files; do not modify global ~/.codex / ~/.copilot configuration unless the user explicitly asks.

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.