init-brain
Skill0 starsChanged 24 days agoMITView on GitHub
Initialise this second brain for a new project from project.yaml. Run once after creating the repository from the template.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Seraght/claude-skillstheir own version, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Seraght/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are 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.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Read project.yaml. If project_name is still My Project or description is empty, ask the user for the project name, a one-sentence …
- Very specific: line 12
If .venv/ does not exist in the project folder, run the setup script for the platform (./scripts/setup.ps1 on Windows, ./scripts/setup.sh …
- Very specific: line 14
Run uv run python tools/kb/bootstrap.py (add --demo only if the user asked for it).
- Very specific: line 17
Ask which systems, parties and concepts recur in this project (or propose them from project.yaml) and add them to tools/kb/entities.yaml …
≈ “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
Arguments: $ARGUMENTS (the text typed after the command; usually empty).
- Read
project.yaml. Ifproject_nameis stillMy Projectordescriptionis empty, ask the user for the project name, a one-sentence description, the main domains (3–8 short slugs) and the owners/teams, write them intoproject.yaml, then continue. - If
.venv/does not exist in the project folder, run the setup script for the platform (./scripts/setup.ps1on Windows,./scripts/setup.shelsewhere) and stop if it fails. - Run
uv run python tools/kb/bootstrap.py(add--demoonly if the user asked for it). It writes the project name into AGENTS.md and the knowledge index, creates thesource/lanes, initialises empty registers, installs the git pre-commit hook and runstools/kb/refresh.py. - Ask which systems, parties and concepts recur in this project (or propose them from
project.yaml) and add them totools/kb/entities.yamlwith their aliases; runuv run python tools/kb/refresh.pyagain. - Reply in ≤ 8 lines: what was set up, and the next step ("drop material in
inbox/, then/ingest all").
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.