capture
Skill1 starsChanged 4 days agoMITView on GitHub
Turn a transcript or note in sources/ into proposed brain entries (decisions, rules, clarifications, code notes) written to brain/inbox/. Use when someone says "capture this", "file this call", or points at a new file in sources/. Never approves anything.
60 other projects use a version of this.
Adopted by
Most recently taken up by
- jakubtobiasz/second-brain-templatetheir own version, first seen Nov 15, 2026
- AndyMelnykov/obsidian-claudetheir own version, first seen Nov 15, 2026
- playingpossumm/loose-endstheir own version, first seen Nov 10, 2026
- jzhao234/big-braintheir own version, first seen Nov 8, 2026
- jskswamy/skillstheir own version, first seen Nov 8, 2026
- kazemcodes/skill-treetheir own version, first seen Nov 8, 2026
Used with
Projects with it also use weekly, ingest 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.
gaiaaiagentSkillweekly
Generate a weekly digest rolling up dailies into higher-level pattern analysis
Also in 4 projects that use this
JaimeGBASkillingest
Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base
Also in 9 projects that use this
AnthropicSkillbrief
Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.
Also in 6 projects that use this
dubwoahSkillask
Answer questions about the codebase without generating or modifying any code. Use when the user wants to understand how something works, find where something is defined, or explore the project structure. Invoked with /ask.
Also in 5 projects that use this
QuixiAISkillweekly-review
Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week
Also in 5 projects that use this
termdockSkillrecall
Retrieves cross-session memories about past decisions, lessons, and patterns. Use when user asks about prior work, past decisions, or mentions a feature. Triggers include check memory, what did we decide, how did we solve.
Also in 6 projects that use this
Other versions60 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 60
- garrytan/gbrain★ 33ksame name
- andreaskelm/pm-brain★ 235same name
- manusco/resonance★ 38same name
- nimbalyst/nimbalyst-wiki★ 36same name
- Hassaan146/claude-skills★ 18same name
- ArcticFox2029/chamnan★ 10same name
- JaimeGBA/Ion★ 9same name
- sunitghub/canon-skills★ 9same name
- philippe-desplats/second-brain★ 6same name
- GavinGreenwood/agentic-workflow-template★ 5same name
50 more not listed
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.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brain-healthSkill
- plan-in-nine-stepsSkill
- write-handoffSkill
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 58 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
- Very specific: line 13
Read AGENTS.md and brain/INDEX.md.
- Distinctive: line 14
Read the source. Find statements that are decisions, rules, answers to questions, or facts about the code.
- Very specific: line 21
Check each proposal against INDEX.md.
- Very specific: line 22
If the source leaves a question open, add a row to brain/open-questions.md with an owner role and whether it blocks.
“Common” is measured: kept by at least 6 in 10 of the 58 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.
Files
Capture
Turns a source into proposals. A person approves them later.
Steps
- Confirm the source file is in
sources/. If not, ask the person to put it there first. - Read
AGENTS.mdandbrain/INDEX.md. Do not open other entries unless step 5 needs them. - Read the source. Find statements that are decisions, rules, answers to questions, or facts about the code. Skip opinions, chatter and anything still undecided.
- For each one, write a file in
brain/inbox/named<D|R|C|K>-<next number>-<short-title>.md, using the front matter in the example entries. Always set:status: proposedandproposed_on(today's date). Neverapproved.scopeas narrow as the source supports (product, area, client). Do not use "all" unless the source clearly says it applies to everything.sourcepointing to the file.- A suggested confirmer in the body: a role or a named person who owns this area.
- The exact line quoted from the source.
- Check each proposal against
INDEX.md. If an approved entry in the same scope would be contradicted or replaced, open that entry and note it in the proposal: "Would replace D-00NN" or "Conflicts with R-00NN". - If the source leaves a question open, add a row to
brain/open-questions.mdwith an owner role and whether it blocks. - Report: how many proposals, their IDs, who should confirm each, any conflicts, any new open questions. Remind the person that nothing counts until they approve it.
Do not
- Set
status: approved, fill inconfirmed_byorconfirmed_on, or move files out of the inbox. - Invent a source line. If you cannot quote one, do not propose the entry.
- Edit the source.
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.

