quick-capture
Skill7 starsChanged 23 days agoMITView on GitHub
Capture a thought, task, idea, or worry into the LifeOS inbox without breaking flow. Use when the owner says "capture", "add to inbox", "note this", "remind me later", or dumps a quick idea. Appends to 06_Trackers/inbox.md and optionally classifies it.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- glodyfimpa/claude-skillstheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- glodyfimpa/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.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- daily-briefSkill
- mission-swapSkill
- setupSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Read 06_Trackers/inbox.md — if it doesn't exist yet (fresh instance ships only templates), create it from 06_Trackers/inbox.template.md …
- Distinctive: line 18
Do not overwrite existing entries — always append.
- Distinctive: line 19
Keep the reply to one or two lines.
- Very specific: line 23
When tagging an area, use only the area codes defined in dashboard/lifeos.config.json (fall back to the .example config if it doesn't …
≈ “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
Quick Capture
Capture anything into the LifeOS with zero friction. The point is to get it out of the owner's head and into the system, then sort later.
Steps
- Read
06_Trackers/inbox.md— if it doesn't exist yet (fresh instance ships only templates), create it from06_Trackers/inbox.template.mdfirst. - Append the captured item as a bullet with a timestamp:
- [YYYY-MM-DD] <text>. - If it's obviously a task, a routine, a reminder, or a someday-item, say so in one line and offer to file it directly. This skill writes vault files; it does not update existing browser tasks/habits. Explain that boundary if the owner expects the dashboard to change (see
docs/browser-data.md):- Task →
06_Trackers/tasks.md(with priority + area code fromdashboard/lifeos.config.json; create the file from its template if missing) - Recurring →
06_Trackers/habits.md - Date-bound →
06_Trackers/reminders.md - Someday → the relevant
02_Areas/note (or a dedicated someday file)
- Task →
- Do not overwrite existing entries — always append.
- Keep the reply to one or two lines. Don't turn a capture into a planning session.
Rules
- Capture the owner's stated priority without automatically parking it until a mission gate. Offer a parking-lot label only if they ask for focus support or choose it themselves.
- When tagging an area, use only the area codes defined in
dashboard/lifeos.config.json(fall back to the.exampleconfig if it doesn't exist).
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.

