capture
Skill2 starsChanged 48 days agoMITView on GitHub
Route a free-form thought, note, observation, meeting fragment, idea, person or project update, or to-do into the right file in this folder. Runs on its own whenever the user types something that reads like a note rather than a question, including pasted meeting exports from Granola, Gong, or Zoom, and also runs on the explicit /capture command. One pass, no inbox, the user's own words preserved.
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
- anurag-rivora/product-brain-startertheir 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
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 repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- annual-reviewSkill
- daily-briefingSkill
- daily-wrapSkill
- monthly-recapSkill
- quarterly-recapSkill
- weekly-recapSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
30 rules. 0 are common, 16 are distinctive, and 14 are very specific to this project.
0
Common
Most of the 58 edited versions we read keep these.
16
Distinctive
This author's own choices. Worth a look.
14
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
If a message carries both a question and a note, answer the question first, then ask whether to capture the rest.
- Distinctive: line 39
When you genuinely cannot tell, ask one short question and wait: "Capture this, or are you asking me something?" Do not guess, and do not …
- Very specific: line 44
Read config/profile.md for the user's name, timezone, life threads, and tag set.
- Distinctive: line 66
Run one, and if the shell rejects the flag, run the other.
- Distinctive: line 71
Check the answer slots, not the file text.
- Distinctive: line 84
Every slot still unfilled, nothing written at all: the user has not been set up.
- Very specific: line 106
If daily/YYYY-MM-DD.md for that day does not exist, create it from the template with that day's date and weekday.
- Very specific: line 144
If the entry records something the user decided, put it under ## Decisions Made instead.
- Very specific: line 164
Add tags to the note's frontmatter from the user's tag set in config/profile.md.
- Very specific: line 170
Create meetings/YYYY-MM-DD - Descriptive name.md.
- Very specific: line 192
Never wikilink the user. They were at their own meeting, and people/ is for other people.
- Distinctive: line 210
Keep the tool's summary, decisions, and action items as written.
- Very specific: line 212
If a full transcript is pasted, keep it under a ## Transcript heading at the bottom of the same file rather than throwing it away or making …
- Distinctive: line 223
When ownership is genuinely unclear on an item, leave it in the note and name it in your confirmation.
- Distinctive: line 226
If the export names attendees you have no file for, say so in the confirmation.
- Very specific: line 231
Look in people/ for an existing file, matching loosely on the name.
- Very specific: line 240
If a standing fact changed, also correct it at the top of the file.
- Distinctive: line 264
When an email connector is present and the user names someone by first name only, you may check recent threads to work out who they mean.
- Very specific: line 295
Only the user's own to-dos go here.
- Distinctive: line 299
Priority: Use what the user said. If they did not say, infer from the words they used, and prefer no marker over a wrong one.
- Distinctive: line 306
No marker: everything else.
- Very specific: line 321
Dedupe: Before appending, compare the new item against every unchecked item in tracker.md.
- Distinctive: line 337
Treat singular and plural as one word.
- Distinctive: line 353
When two items share only a name, or only a verb you were about to strip anyway, they are different items, so write the new one.
- Very specific: line 370
No checkbox on this line. tracker.md owns the item from here on, and ticking it off there never ticks this copy, so a checkbox here would …
- Very specific: line 402
If you made a call the user might disagree with, add one line and stop there: Assumption: filed as a daily entry, not a meeting.
- Distinctive: line 406
Do not summarize the input back.
- Very specific: line 426
Run these as separate commands, never chained with &&.
- Distinctive: line 436
Never discard content. Everything they typed ends up somewhere.
- Distinctive: line 443
No em dashes and no double hyphens in anything you write.
“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
Take whatever the user just typed and file it, in one pass, in their words. There is no inbox and no second sort. By the time you reply, the note is in its final home, linked, and committed.
When this runs
Two triggers, same logic.
Ambient. Any message that reads like a thought, an observation, a meeting fragment, an idea, or a to-do routes here automatically. No command needed.
Explicit. /capture <text> forces this path even on a message that could
read as a question.
Do not capture:
- Direct questions ("what do you think about this?", "who is Nadia again?"). Answer them. Afterward you can ask whether to save anything from the exchange.
- Slash commands.
- Edit instructions ("change that heading", "add this line to the tracker").
- Conversation about how this system works.
If a message carries both a question and a note, answer the question first, then ask whether to capture the rest.
One exception to the list above. When the user says a thing the briefing raised is already handled ("did that yesterday", "that's done, stop flagging it"), it reads like talk about the system, but it is a fact about their life. Capture it as a daily entry in their words. The briefing reads the notes, so that entry is what stops the flag.
When you genuinely cannot tell, ask one short question and wait: "Capture this, or are you asking me something?" Do not guess, and do not do both.
Before you start
Read config/profile.md for the user's name, timezone, life threads, and tag
set. Read config/season.md for what this stretch is about, which tells you
whether a passing mention belongs to something they are actively tracking.
Get the timezone out of config/profile.md and pass it to date through Bash,
so the clock on the machine never decides what day it is. With
Europe/Lisbon in the profile:
TZ=Europe/Lisbon date +%Y-%m-%d
TZ=Europe/Lisbon date +%ASubstitute whatever zone the profile names. Bare date +%A is wrong. Never read
a weekday off an ISO string. If the profile has no timezone in it, stop and ask
for one, then carry on once they answer. Never guess a zone and never fall back
to the machine clock, because a capture filed to the wrong day looks correct and
stays wrong.
Date arithmetic is not portable, so any day other than today needs care. On macOS
the shell has BSD date and takes TZ=Europe/Lisbon date -v-1d +%Y-%m-%d. On
Linux it has GNU date and takes TZ=Europe/Lisbon date -d yesterday +%Y-%m-%d.
Run one, and if the shell rejects the flag, run the other. Do not do the
arithmetic in your head instead.
When the config is not fully filled
Check the answer slots, not the file text. Both config files carry instruction
comments that describe the placeholder markers in prose, and those comments stay
there forever, so a plain search for that shape matches on a fully configured
vault every time. Look at what sits under each heading instead. Nothing in
config/templates/ is config: those slots are filled by skills on every run, so
never read them as setup answers.
A slot counts as filled when it holds anything the user put there, and
(skipped) is something the user put there. Treat it as a filled answer, a
deliberate pass on an optional question, never as a blocker.
Then degrade rather than stop:
- Every slot still unfilled, nothing written at all: the user has not been set up. Say so in one line, offer the setup interview in CLAUDE.md, and stop.
- Some filled, some not: capture with what is there. No tag set means you write the note without tags and propose one in your confirmation. No life threads means a tracker item goes in without a thread section. No season means you file it without the season lens and say nothing about it.
The one gap you cannot work around is the timezone, because every path in this skill writes a date. Ask for it, wait, and do not guess.
A partly filled profile is a normal state, not an error.
Backdating
Most captures are about today. When the input says otherwise ("yesterday", "Monday night", "this happened on the 3rd"), write it to that day's note instead of today's.
- Resolve the phrase with the same timezone aware
datecall, in the portable form above, never by counting in your head. - For "yesterday" or an outright date, just write it. For anything loose ("last week", "a few days ago"), say the resolved date back in one line first and wait.
- If
daily/YYYY-MM-DD.mdfor that day does not exist, create it from the template with that day's date and weekday. - Everything else in this skill works the same. Cross links point at that day's note, not today's.
- On a tracker item, the
captured:stamp keeps the real date you wrote it. Only the daily note moves.
Step 1: classify
Pick exactly one primary destination. If two are equally plausible, ask one question.
| Type | Signal | Goes to |
| Daily entry | A thought, an observation, a thing that happened. The default when nothing else fits. | daily/YYYY-MM-DD.md |
| Meeting note | "Just got off a call with", "met with", or a pasted export from a note-taker. | meetings/YYYY-MM-DD - Name.md |
| Person update | New standing context about someone: a role change, what they are working on, how they think. | people/Name.md |
| Project update | Movement on something with a finish line: state, a decision, a next step. | projects/<project>.md |
| Reference or idea | A link, a quote, a seed of an idea with no date and no owner. | notes/<slug>.md |
| Action item | Something the user has to do. A verb phrase. "I need to", "remind me to", "follow up with". | tracker.md |
Rule of thumb: if it happened today or the user thought it today, the daily note is the primary home and everything else gets a cross-link. Route away from the daily note only when the content is a standing asset, meaning something worth reading a year from now outside the day it arrived.
One input can produce more than one write. A meeting note that contains a commitment produces a meeting file, a tracker item, and a line in the daily note. That is normal.
Step 2: route
Daily entry
Find or create daily/YYYY-MM-DD.md from config/templates/daily-note.md,
filling {{date}} and {{weekday}}. Append the content verbatim under
## Entries, newest at the bottom.
If the entry records something the user decided, put it under ## Decisions Made
instead. That heading is a top level section of the daily note and it sits
directly before the ## End of Day Reflection section. Create it there if it is
not there yet, and append to it if it is. Never open a second one. Keeping it
above the reflection means a note captured at two in the afternoon reads top to
bottom, with the one empty heading the wrap has not reached yet sitting last
where it belongs. The weekly recap harvests decisions by that exact heading name,
so the wording matters most of all.
Wikilink every person, project, and company: [[Nadia Okonkwo]], [[kitchen
remodel]]. If the linked file does not exist, still write the link, and mention
in your confirmation that the note is missing. Do not wikilink the user
themselves.
Link names, not roles. "The deputy principal", "my landlord", "the new starter"
are descriptions of a person, not a person's name, and [[deputy principal]]
points at a file nobody will ever open. Leave a role reference as plain text. If
the same role shows up a second time, offer once to attach a name to it so future
mentions can link, and if they pass, drop it and do not ask again.
Add tags to the note's frontmatter from the user's tag set in
config/profile.md. Do not invent a tag. If nothing fits, propose one in your
confirmation and wait.
Meeting note
Create meetings/YYYY-MM-DD - Descriptive name.md. Sentence case, meaning you
capitalize the first word and any proper nouns and nothing else. Spaces, no
slugs: meetings/2026-03-14 - Roof estimate with Dana Whitfield.md. Ordinary
punctuation is fine, so meetings/2026-04-02 - Dad's power of attorney.md is a
good filename. Leave out the characters that break filesystems: slashes, colons,
asterisks, pipes, angle brackets, and quotation marks. If a file for that
conversation already exists, append rather than making a second one.
---
type: meeting
date: 2026-03-14
tags: ["#work"]
---In the body, keep the user's text verbatim under whatever structure is already
there. If the input has no structure, one heading is enough. Useful headings when
the content supports them: ## What was discussed, ## Decisions,
## Next steps. Wikilink every attendee in the body. Attendees live in the body,
not in frontmatter.
Never wikilink the user. They were at their own meeting, and people/ is for
other people. If a pasted export lists them in the attendee line, leave their
name as plain text.
Then add one line to today's daily note under ## Entries:
- Met with [[Dana Whitfield]] about the roof estimate, see [[2026-03-14 - Roof estimate with Dana Whitfield]]Apply the person rules below to each named attendee, and pull the user's own
commitments out into tracker.md.
Pasted note-taker exports. Granola, Gong, and Zoom output all land here. Signals: an attendee list at the top, speaker labels, timestamps, a block titled summary or call brief, or the user saying "here are my notes from". Treat the paste as a meeting note, not a daily entry.
- Keep the tool's summary, decisions, and action items as written. Drop only the product's own chrome, meaning banners, share links, and marketing footers.
- If a full transcript is pasted, keep it under a
## Transcriptheading at the bottom of the same file rather than throwing it away or making a second file. - Pull only the action items the user owns into
tracker.md, one line each, with any other person wikilinked.tracker.mdis the user's to-do list and nothing else. An item belongs to the user when they said they would do it, when the export assigns it to them by name, or when it is unassigned and clearly theirs from the context. - Everyone else's action items stay in the meeting note, under the export's own heading, exactly as written. They are still a record, they are just not the user's work. Say which ones you left there in your confirmation, for example "2 items to tracker.md, 3 left in the note as other people's".
- When ownership is genuinely unclear on an item, leave it in the note and name it in your confirmation. Better a missed to-do the user can see than a tracker they stop trusting.
- If the export names attendees you have no file for, say so in the confirmation. Do not create person files for everyone in a large invite list.
Person update
Look in people/ for an existing file, matching loosely on the name. If it
exists, append a dated entry:
## 2026-03-14
Moved off the day shift to nights. Runs the triage rotation now.If a standing fact changed, also correct it at the top of the file. If there is
no file, create people/Name.md:
---
type: person
date: 2026-03-14
tags: ["#work"]
---
# Nadia Okonkwo
Where they work, what they do, how the user knows them. Only what is known.
## 2026-03-14
[The captured content, in the user's words.]Fill in what you were told and nothing else. An empty line beats an invented one.
Then surface a line in today's daily note under ## Entries so the day stays a
complete record.
When an email connector is present and the user names someone by first name only, you may check recent threads to work out who they mean. If one person clearly matches, use the full name. If two might, ask. Never write an address into a file unless the user gave it to you or the match was unambiguous.
Project update
Append to projects/<project>.md, or to status.md and decisions.md if that
project already uses a folder. State goes in the status section; a decision gets
its own dated entry with one to three sentences of reasoning, because in six
months the reasoning is the part worth having.
Surface a line in today's daily note. If the content implies a project that does not exist yet, flag it and ask before creating anything. Do not create top level folders on your own.
Reference or idea
A reusable reference goes to notes/<slug>.md with type: note, the date, and
tags. A fleeting idea goes under ## Entries in today's daily note instead. Do
not create a file per stray thought.
Action item
Append to tracker.md under the thread section that fits, using the thread names
from config/profile.md. Create a section only when a thread has its first item.
- [ ] Send [[Dana Whitfield]] the roof measurements !high due:2026-03-20 <!-- captured: 2026-03-14 -->Only the user's own to-dos go here. If the input names something someone else
owes them, that is a fact for the person note or the meeting note, not a line in
tracker.md.
Priority. Use what the user said. If they did not say, infer from the words they used, and prefer no marker over a wrong one.
!high: important, critical, urgent, asap, must do, cannot forget, blocking, deadline, high priority, or "need to" plus today, tomorrow, or this week.!med: should do, need to get to, would like to, plus a near term timeframe.!low: someday, maybe, would be nice, if I get time, no rush, eventually.- No marker: everything else.
Due dates. Resolve relative phrases against today's date, then delete the phrase from the item text so the line reads cleanly.
- today, tomorrow: today, today plus one.
- "by Friday" and other weekdays: the next occurrence of that weekday. Confirm it
with the timezone aware
datecall above, never by counting in your head. - "this week" and "by EOW": the coming Friday. "next week": Friday of next week. That is an assumption about where their week ends, not a fact, so say it once when you use it and take whatever they tell you instead.
- "end of month": the last day of the current month.
- "in N days" or "in N weeks": today plus N days, or N times seven.
MM/DD: this year if it has not passed, otherwise next year.
Dedupe. Before appending, compare the new item against every unchecked item
in tracker.md. A raw text match does not work here, because the stored line
carries wikilinks and metadata the user never typed. Normalize both sides first:
- Strip
[[and]], so[[Dana Whitfield]]becomesDana Whitfield. - Strip the metadata, meaning
!high,!med,!low,due:..., the checkbox, and the<!-- captured: ... -->comment. - Lowercase and drop punctuation.
- Drop filler words: a, an, and, the, to, for, from, my, our, their, this, that, these, those, with, about, on, in, at, of, some, any, re, please, need, needs, want, get, got.
- Drop the first remaining word on both sides. Action items open with a verb, and the verb is the part users swap without meaning anything by it, so "email Rangi about the trip forms" and "send Rangi the trip form email" should land on the same remainder rather than reading as two jobs. Only the first word goes.
- Treat singular and plural as one word. Trim a trailing "s" or "es" off every word that survives, so "form" and "forms" compare equal. It is crude and it will occasionally mangle a word, which costs nothing here because the output is only ever compared against another string put through the same steps.
Compare what is left as a set of content words. If one set contains the other, it
is the same item: skip the write and say so in your confirmation. So "send Rangi
the trip form email" reduces to rangi trip form email and a stored "Email Rangi
about the trip forms" reduces to rangi trip form, which is contained in the
first, so it is a duplicate. Do not create a near duplicate with different
wording.
This is a heuristic and it will land in the middle sometimes. When the two sets overlap heavily but neither contains the other, do not decide for them. Surface it and wait: "This looks close to 'Email Rangi about the trip forms', already on the list. Same thing, or a separate item?" Never drop a to-do on a partial match. When two items share only a name, or only a verb you were about to strip anyway, they are different items, so write the new one.
Moving a date. "Push the roof measurements to Friday" or "pull the permit
call in to Tuesday" is an edit to the line already in tracker.md, not a new
item. It reads like an edit instruction, but handle it here, because it is the
same line capture wrote. Find it the same way dedupe does, change due: in place, and leave the
captured: stamp alone. Never append a second copy with the new date. If you
cannot find the item, say so and ask whether to add it as new.
Then add a line under ## Entries in today's daily note pointing at the tracker,
so the day reads as a complete record without splitting the truth:
- To-do: Send [[Dana Whitfield]] the roof measurements, see [[tracker]]No checkbox on this line. tracker.md owns the item from here on, and ticking it
off there never ticks this copy, so a checkbox here would sit open forever and
read as a dropped to-do to anything that scans the daily notes.
Output
One or two lines. What you wrote, where, and what you linked.
Captured -> daily/2026-03-14.md, linked [[Nadia Okonkwo]]Captured -> meetings/2026-03-14 - Roof estimate with Dana Whitfield.md, 1 item to tracker.md, 2 left in the note as other people'sCaptured -> tracker.md under Home, !high due:2026-03-20Already in tracker.md: "send Dana the roof measurements". Nothing written.Moved in tracker.md: "send Dana the roof measurements", due:2026-03-20 -> due:2026-03-27Captured -> daily/2026-03-13.md (yesterday), linked [[Nadia Okonkwo]]If you made a call the user might disagree with, add one line and stop there:
Assumption: filed as a daily entry, not a meeting. Say the word and I will move
it.
Do not summarize the input back. Do not reflect on it. Do not coach. Ask at most one question per capture, and ask it before you write, not after.
Commit
After the writes:
Stage the files you actually touched, by path. Never git add -A, because it
sweeps up whatever else is sitting in the folder. Put every path in single
quotes, because meeting filenames have spaces in them, and never escape a space
with a backslash:
git add 'daily/2026-03-14.md' 'meetings/2026-03-14 - Roof estimate with Dana Whitfield.md' 'tracker.md'git commit -m "capture: roof estimate with Dana"Run these as separate commands, never chained with &&. The message is three to
seven words describing what was captured. Then check for a remote. Push only to
a remote the user owns, as its own command, and if there is none, say nothing
about it.
Tone and format rules
- Verbatim wins. If they wrote "today was a slog", the file says "today was a slog", not "the day presented some challenges". Their phrasing is the whole point of keeping the record.
- Never discard content. Everything they typed ends up somewhere.
- Cross link every route. A meeting note with no line in the daily note, or a person update that never surfaces, is a bug.
- Frontmatter stays at three fields:
type,date,tags. Tags are a quoted inline array. Resist adding fields. - Structure is the value, not length. Do not pad a two line thought into a section.
- No em dashes and no double hyphens in anything you write. Commas, parentheses, or a new sentence.
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.

