obsidian-capture
Skill8 starsChanged 35 days agoMITView on GitHub
Save a note, decision, or thought to the Obsidian vault right now. Use when someone says "capture this", "save this to Obsidian", "note this down", "log this decision", "obsidian note", "save this for later", "capture that idea". Requires OBSIDIAN_VAULT_PATH to be set.
- Reads credentials
4 other projects use a version of this.
Adopted by
Most recently taken up by
- ddenzu/karpathy-llm-wiki-second-braintheir own version, first seen Nov 8, 2026
- aiqianqian521/obsidian-skillstheir own version, first seen Nov 1, 2026
- wilbeibi/wilbeibi-skillstheir own version, first seen Sep 7, 2026
- willsu88/skillstheir own version, first seen Jul 31, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- ddenzu/karpathy-llm-wiki-second-brain★ 6same name
- wilbeibi/wilbeibi-skills★ 2same name
- willsu88/skills★ 2same name
- aiqianqian521/obsidian-skills★ 1same 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 repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- backlogSkill
- conventionsSkill
- debugSkill
- devops-azureSkill
- devops-githubSkill
- devopsSkill
- hotfixSkill
- implementSkill
- interview-meSkill
- lint-agentsSkill
- memory-auditSkill
- memory-querySkill
- obsidian-briefSkill
- obsidian-dailySkill
- obsidian-recapSkill
- obsidian-searchSkill
- obsidianSkill
- onboardSkill
- pack-reviewSkill
- planSkill
- refactorSkill
- repo-mapSkill
- review-prSkill
- scaffoldSkill
- setup-projectSkill
- smellSkill
- spec-intakeSkill
- system-checkSkill
- whatSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
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 18
Read OBSIDIAN_VAULT_PATH from the environment:
- Distinctive: line 22
If empty, stop and tell the user:
- Distinctive: line 38
Ask the user: "What do you want to capture?"
- Very specific: line 78
Never pass OBSIDIAN_REST_API_KEY to obsidian-writer.
- Very specific: line 80
If obsidian-writer reports the vault directory doesn't exist, tell the user to verify the path in ~/.claude/settings.json.
“Common” is measured: kept by at least 6 in 10 of the 3 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
Obsidian Capture
Save an ad-hoc note, decision, or thought to the vault immediately. Captures
always land in Claude/captures/ (global, not project-specific) and are linked
into the project's daily note automatically.
Step 1 — Check configuration
Read OBSIDIAN_VAULT_PATH from the environment:
- Bash:
bash -c 'echo $OBSIDIAN_VAULT_PATH' - PowerShell:
$env:OBSIDIAN_VAULT_PATH
If empty, stop and tell the user:
"OBSIDIAN_VAULT_PATH is not set. Re-run
install.shand provide your vault path when prompted, or add it manually to~/.claude/settings.jsonunder theenvkey."
Also read:
OBSIDIAN_PROJECTS_FOLDER(empty string if unset — used for daily note routing)
You do not need the REST API variables. obsidian-writer owns the transport chain
(CLI → REST API → filesystem) and reads OBSIDIAN_REST_API_KEY, OBSIDIAN_REST_API_PORT,
and OBSIDIAN_REST_API_HTTPS from the environment itself. Never pass the API key to an
agent — it would end up in the dispatch payload and the transcript.
Step 2 — Collect content
Ask the user: "What do you want to capture?"
Accept a title and body, or just body text (title will default to the first line of the body if not provided separately).
Step 3 — Dispatch obsidian-writer
Invoke the obsidian-writer agent with:
write_mode:capturevault_path: value ofOBSIDIAN_VAULT_PATHprojects_folder: value ofOBSIDIAN_PROJECTS_FOLDER(empty string if unset)title: user's titlebody: user's body textproject: basename of current working directorytimestamp: current datetime inYYYY-MM-DDThh:mmformat
That is the whole step. Do not attempt the REST API here — obsidian-writer tries the Obsidian CLI, then the REST API, then the filesystem, and reports which one succeeded. Building the capture markdown, choosing a transport, and verifying the write are all its job.
Step 4 — Confirm
Report the file path and the transport obsidian-writer reported. Example:
"Captured to
Claude/captures/2026-05-14-1430.md(via Obsidian CLI)"
or:
"Captured to
Claude/captures/2026-05-14-1430.md(filesystem — CLI and REST API unavailable)"
Pass the transport through rather than guessing it. If obsidian-writer reports it degraded to the filesystem, say why in the same line — a silent permanent degradation is invisible otherwise.
Gotchas
- Capture files always go to
Claude/captures/— they are not project-scoped. - Do not attempt the REST API in this skill. It used to, and that duplicated transport logic in every calling skill. obsidian-writer owns the whole chain now; a REST attempt here would run before the dispatch and so defeat the CLI-first ordering entirely.
- Never pass
OBSIDIAN_REST_API_KEYto obsidian-writer. It reads the key from the environment precisely so the secret stays out of the dispatch payload and the transcript. - If obsidian-writer reports the vault directory doesn't exist, tell the user
to verify the path in
~/.claude/settings.json.
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.

