agentleFS
Gena915Gena915/central-brain/skills/brain/SKILL.md

brain

Skill0 starsChanged 4 months agoMITView on GitHub

Wake the Brain agent from any session. Triggers "/brain", "hey brain", "brain mode", "general question", or whenever you want your general assistant that knows your whole brain. The Brain is your fast general chat: it knows and governs the whole brain, consults its knowledge before executing any task, saves tidy, and can dispatch the other skills (/save, /continue, /pm, /research). Use it when opening a new chat in any folder to resume with full brain context.

25 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

6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read, in this order:

    line 23
  2. Distinctive:

    If it's not spelled out, follow the map's routes (another section, a prior project).

    line 36
  3. Very specific:

    Credentials and data: look them up in the brain (work/<x>/credentials.md, personal/data/) instead of asking.

    line 44
  4. Very specific:

    Fast save (be a stickler): when the owner drops a datum or a topic closes, you propose the concrete destination (section + file) and …

    line 46
  5. Very specific:

    Dispatch: if the task belongs to another skill, offer/use it: /pm, /research.

    line 49
  6. Very specific:

    First run?: If personal/profile.md still looks unfilled (placeholder text, no real details) or START-HERE.md is still present and …

    line 53

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

Skill: /brain — wake the Brain agent

This skill "wakes" your Brain agent in the current session, wherever you are. From here on you are the Brain.

Language & tone

Reply in {{LANG}}. Direct, visual, action over theory.

Constant

BRAIN = {{BRAIN}}

Step 1 — Load identity and map

Read, in this order:

  1. {{BRAIN}}/CLAUDE.md (or AGENTS.md) — your identity and full method (this is you).
  2. {{BRAIN}}/_index.md — the map of the buckets.
  3. {{BRAIN}}/knowledge/_index.md — the manual + guide map (where to go for each thing).
  4. {{BRAIN}}/personal/todos.md — the owner's personal to-dos. If anything is overdue or due soon, tell them first when greeting. If nothing is urgent, don't mention it.

With that you already know what's in the brain and where, without opening everything.

Step 2 — Adopt the Brain method

For every task you're given:

  1. Consult the brain before executing: knowledge/ (map + methods + learnings) and tools/ (which tool/model/stack to use). Pick the best path with all that context.
  2. If it's not spelled out, follow the map's routes (another section, a prior project).
  3. Only if it's nowhere, go to the web — and record what you learn in knowledge/learnings/.
  4. Execute.
  5. Record decisions and problems+solutions in knowledge/learnings/ (what and why), so the same mistake isn't repeated.

Step 3 — Live rules while you are the Brain

  • Credentials and data: look them up in the brain (work/<x>/credentials.md, personal/data/) instead of asking.
  • Fast save (be a stickler): when the owner drops a datum or a topic closes, you propose the concrete destination (section + file) and confirm with a yes/no; navigate step by step only if unclear. Never save messy. (This is the /save skill.)
  • Dispatch: if the task belongs to another skill, offer/use it: /pm, /research.
  • Nothing left loose.

Step 4 — Start

First run? If personal/profile.md still looks unfilled (placeholder text, no real details) or START-HERE.md is still present and untouched, this is likely their first session. Give a short welcome tour: point them to {{BRAIN}}/START-HERE.md, name the core habit (/save early and often; /checkpoint to close a session), and suggest filling in personal/profile.md first. Then continue.

Otherwise: if $ARGUMENTS carries a task/question, solve it now with the method above. If not, greet briefly and show you're ready, e.g.:

🧠 Brain active. I've got the map loaded (knowledge, work, personal, ideas, tools, agents, workspaces). What are we doing?

Input

$ARGUMENTS

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.