Capture
Claude Code skills I wrote and use daily — plus notes on how the skill system is designed. Copy anything.
npx -y skills add Chevis-Zhou/agent-skills --skill captureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 21 days oldThe repository was created 21 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Fast triage for a pasted thought, dropped file, or pointed-to content — classify it and route it to the right store. Use when the user says "capture this", "/capture", or hands over a stray idea/note/asset with no clear domain already stated. If they name the destination explicitly, use that route directly instead — capture is only for the undecided case.
SKILL.md
3.5 KB, 715 tokens by cl100k_base, as published. Nobody here has run it
Capture
Speed is the point. No negotiation, no restructuring, no summarizing back the content. Classify, route, append, confirm — one line.
Adapt the routing table. The buckets below are the four stores in my system — replace the destinations with your own (drafts folder, project TODOs, client inboxes, knowledge base). The pattern is what matters: a closed set of buckets, one destination each, ask at most one question.
Classify
Match the input to exactly one bucket:
| Type | Signal | Destination |
|---|---|---|
| Article draft | Long-form prose/idea on a design/dev/career topic, no specific project task attached | {drafts-dir}/{slug}.md — new file if the slug doesn't exist, else append with a --- separator |
| Project todo | A short task, bug, or backlog idea tied to a specific project | That project's TODO.md, appended under the relevant section (default: ## Someday if no section fits). If the project isn't stated or obvious from content, ask once which project. |
| Client asset | Content or a file tied to a named client | {clients-dir}/<slug>/inbox/ (per your workspace registry's routing map) |
| Reference / knowledge | An evergreen fact, concept, or thought worth preserving, not tied to any project or client | {wiki-dir}/raw/{domain}/sources/ — infer domain from content; if ambiguous, check for the closest existing domain dir |
If none of the four fit or the classification is genuinely ambiguous: ask ONE question naming the buckets, then proceed. After routing, add a row to your registry's routing map for the keyword/pattern that triggered the ambiguity — so the next capture of this shape doesn't need to ask.
Route
- Locate the destination file per the table above (create it if it's a new slug/todo/domain — don't ask permission for routine appends, this store is a machine-side queue).
- Append the content as-is, or lightly wrapped (e.g. a
## {date}heading for a wiki source drop) — do not rewrite, restructure, or edit the substance of what was captured. - For client assets that are files (not text), move the file into the inbox; don't copy-and-leave-original.
Confirm
Reply with exactly one line: destination path + a one-line summary of what was captured. No preamble, no restating the classification logic, no "let me know if...".
Example: → content/_drafts/ai-pair-programming-tells.md — new draft: AI tells in generated prose
Edge cases
- Multiple items in one drop — classify each independently; one confirm line per item. Don't force them into one bucket.
- File (not text) that isn't a client asset — move it (don't copy) into the destination dir; for wiki sources, drop into
raw/{domain}/sources/with the original filename. - Destination explicitly named by the user — skip classification entirely and route where they said; this skill's table is for the undecided case only.
- Content that is both a todo and a reference — todo wins (actionable beats archival); optionally note "also wiki-worthy" in the confirm line rather than double-filing.