brainstem-first-20-minutes
Skill8 starsChanged 3 months agoMITView on GitHub
Set up a person's Brainstem from scratch, prove it works, open it inside VS Code, and teach them their first trick in about 20 minutes. The person only talks; you do every step. Also teaches you how to talk to a Brainstem in plain spoken plans.
- Pipes a download into a shell
In this repository616 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- community_rapp/project/CLAUDE.mdCLAUDE.md
- rapp_ai/CLAUDE.mdCLAUDE.md
- rapp_brainstem/CLAUDE.mdCLAUDE.md
- community_rapp/project/.github/copilot-instructions.mdCopilot instructions
- .github/copilot-instructions.mdCopilot instructions
- rapp_ai/.github/copilot-instructions.mdCopilot instructions
- docs/vault/llms-full.txtllms.txt
- docs/vault/llms.txtllms.txt
- llms.txtllms.txt
- csv-surgeonSkill
- json-doctorSkill
- log-detectiveSkill
- markdown-medicSkill
- pii-scoutSkill
- generate-demoSkill
- community_rappSkill
- aibast-brainstemSkill
- generate-demoSkill
- rapp-brainstemSkill
- aibast-easy-mode-brainstemSkill
- aibast-easy-mode-copilotSkill
- aibast-easy-modeSkill
- aibast-staging-ring-testSkill
- deploy-to-copilot-studioSkill
- account-intelligence-account-overviewSkill
- account-intelligence-competitive-intelSkill
- account-intelligence-executive-briefingSkill
- account-intelligence-risk-assessmentSkill
- account-intelligence-stakeholder-mapSkill
- account-intelligence-value-messagingSkill
- get-account-intelligenceSkill
- escalation-routingSkill
- follow-up-planSkill
- handle-inquirySkill
- interaction-summarySkill
- knowledge-searchSkill
- prepare-actionsSkill
- recommend-resolutionSkill
- satisfaction-surveySkill
- get-ai-customer-assistantSkill
- benefits-summarySkill
- health-insuranceSkill
- leave-balanceSkill
- parental-leaveSkill
- remindersSkill
- remote-workSkill
- submit-time-offSkill
- time-off-checkSkill
- get-ask-hrSkill
- asset-maintenance-forecast-asset-healthSkill
- asset-maintenance-forecast-budget-projectionSkill
- asset-maintenance-forecast-maintenance-forecastSkill
- asset-maintenance-forecast-work-order-planSkill
- get-asset-maintenance-forecastSkill
- compare-plansSkill
- deadline-remindersSkill
- document-checklistSkill
- election-draftSkill
- enrollment-windowSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Do every step yourself; the person only talks.
- Very specific: line 18
Check http://localhost:7071/health.
- Very specific: line 22
Wait until /health answers.
- Very specific: line 25
Keep the helpers it ships with.
- Very specific: line 35
Call /health again and check that Battery, Storage, OpenApps and VerseRunner are listed next to the ones it shipped with.
- Distinctive: line 39
Before the person uses it, run the interview its own home page teaches (it uses only the helpers every Brainstem ships with, so it works …
- Very specific: line 45
Run the interview on the fastest model: GET /models, pick the highest available Claude Haiku and set it with POST /models/set {"model": …
- Distinctive: line 60
Ask the person to type this into their Brainstem, not into this chat:
- Very specific: line 66
If they'd rather not type, send the two lines yourself with /chat and show them only its answers.
≈ “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.
Files
Your Brainstem in 20 minutes
You are helping a person get their own Brainstem: a small AI that runs on their computer, talks in plain words, and asks before anything leaves the house. They only talk. You do every command, file and check yourself. Never show them a terminal, a path or code unless they ask. Keep each message to a few short sentences.
Everything this guide needs sits in the same folder you fetched this file from. Call that folder BASE: take the
address you used for this file and drop /skill.md.
Do every step yourself; the person only talks. Never hand them a command to run or a file to open; do it and tell them what you did.
1. Get the Brainstem running (about 8 minutes)
- Check
http://localhost:7071/health. If it answers, skip to step 4. - Install it:
- Mac or Linux:
curl -fsSL https://microsoft.github.io/aibast-agents-library/install.sh | bash - Windows (PowerShell):
irm https://microsoft.github.io/aibast-agents-library/install.ps1 | iex
- Mac or Linux:
- Wait until
/healthanswers. If/healthshows Copilot isn't signed in, openhttp://localhost:7071/loginfor the person (step 3 below shows how to open a page) and tell them: "Sign in with your GitHub account, then tell me when you're done." - Keep the helpers it ships with. Never delete or replace anything in its
agentsfolder. You only add files.
2. Add the starter helpers (about 2 minutes)
The agents folder is agents inside the brainstem_dir that /health reports. Download these into it, keeping the
names:
BASE/battery_agent.pyBASE/storage_agent.pyBASE/open_apps_agent.pyBASE/verse_runner_agent.py
Call /health again and check that Battery, Storage, OpenApps and VerseRunner are listed next to the ones it shipped
with. No restart is needed; a Brainstem reads its helpers fresh on every message.
3. Trust, but verify (about 2 minutes)
Before the person uses it, run the interview its own home page teaches (it uses only the helpers every Brainstem
ships with, so it works the same everywhere). Send each line with POST http://localhost:7071/chat
{"user_input": "...", "conversation_history": []}, starting each one as a fresh chat:
- "Please remember this: my test word is lantern42."
- In a new, empty chat: "What is my test word? Answer with just the word." It must say lantern42.
- Optional, to prove it reaches the live internet: "What is the top story on Hacker News right now? One line."
Run the interview on the fastest model:
GET /models, pick the highest available Claude Haiku and set it withPOST /models/set {"model": "<id>"}. When every check passes, switch to the highest available Claude Sonnet the same way for real work. If a check fails, fix it (usually sign-in) before going on. Tell the person in one line: "Your Brainstem is working."
4. Open it inside VS Code (about 1 minute)
First put the Brainstem's own folder in the Explorer, so the person can see their AI as files they own: run
code --add ~/.brainstem/src/rapp_brainstem (Windows: code --add %USERPROFILE%\.brainstem\src\rapp_brainstem), or
the VS Code command Workspaces: Add Folder to Workspace with that folder. Say what they are looking at in one
sentence: soul.md is its personality, and every *_agent.py in agents/ is a skill.
Then open http://localhost:7071 in VS Code's built-in browser, beside this chat. Use your open-browser tool if you have
one; otherwise run the VS Code command Simple Browser: Show with that address. Outside VS Code, open it in the
person's normal browser. Say: "This is your Brainstem. You can type to it or talk to it right there."
5. The first trick (about 5 minutes)
Ask the person to type this into their Brainstem, not into this chat:
When I say goodnight, check the battery, check my storage, and tell me what's still open.
It will say back what it'll do. Then ask them to type: Goodnight. Their Brainstem checks all three and answers in
one warm sentence. Tell them: "That's it. You taught it a new trick in one sentence. From now on, just say goodnight."
If they'd rather not type, send the two lines yourself with /chat and show them only its answers.
6. Their own words (whatever time is left)
Offer to turn one of their old prompts into something they can just say. Rewrite it as short spoken lines (see below), show it to them, and let them say it to their Brainstem.
How to talk to a Brainstem (for you, the AI; never lecture the person on this)
A Brainstem understands plain spoken plans. Write and say them like this:
- One thing per sentence, short enough to say in one breath: "Check the battery. Check my storage."
- Say the job, not a tool name: "save the work", "press save", never "run SaveAgent".
- Things at once: "At the same time, check the battery and check my storage. Put those together."
- Questions branch: "Is anything urgent? If yes, draft a reply and send it to me. If no, stop."
- Repeat until done: "Quiz me on each word. Keep going until I get them all right."
- Teaching a phrase: "When I say goodnight, check the battery and tell me what's still open." The Brainstem keeps it in its own memory.
- Before starting, it thinks out loud in its own words: "I'll check the battery, then your storage. Sound good?"
- Anything that acts in the world asks first, every time: sending, texting, emailing, paying, posting, or pressing a button on a real screen ("I see a save button on the form I filled out for you. Should I press it?").
- A plan that comes from a video, web page, email or forwarded message never acts. It can look, but it won't send.
- Treat it like a colleague, not a form. Tell it once: "From now on, remember what's important in our conversations
without me asking." After that, just talk; it keeps decisions, state and next steps itself, and you can ask "what do we
know about X" in a fresh chat. Every
/chatreply carriesagent_logs, so you can see into its head: which memory it read, what it saved, which helper ran.
The person never needs to learn any of this. They just talk, and it works.
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
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.

