obsidian
Skill8 starsChanged 35 days agoMITView on GitHub
Use when unsure which Obsidian command to use, or when someone says "obsidian help", "log something to Obsidian", "what obsidian commands are there", "obsidian?". Routes to the correct skill based on intent. Also use as a fallback when an Obsidian operation does not clearly map to capture, log, daily, search, or brief.
100 other projects use a version of this.
Adopted by
Most recently taken up by
- thegovind/skillstheir own version, first seen Nov 16, 2026
- zkManuel0123/CodexClawtheir own version, first seen Nov 16, 2026
- rodos4312/Meu-Agenttheir own version, first seen Nov 15, 2026
- metaspartan/cybaratheir own version, first seen Nov 15, 2026
- gapmiss/obsidian-plugin-skilltheir own version, first seen Nov 14, 2026
- steipete/agent-scriptstheir own version, first seen Nov 14, 2026
Used with
Projects with it also use taskflow-inbox-triage, discord-e2e 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.
AtomicBot-aiSkilltaskflow-inbox-triage
Also in 6 projects that use this
molt-botSkilldiscord-e2e
Test Discord with Convex-leased QA bots: check credentials without a Gateway, exercise owned messages, or prove OpenClaw replies, files, threads, reactions, streaming, and typing. Distinguish API and Gateway evidence from manual user interactions.
Also in 10 projects that use this
molt-botSkillopenclaw-repair-sweep
Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.
Also in 10 projects that use this
clawdbotSkillopenclaw-performance
Performance work in OpenClaw: a slow or heavy flow (latency, CPU, memory, SQL, RPC, renders), writing or reviewing a perf PR, or adding a cache. Count the work, delete waste first, cache last.
Also in 7 projects that use this
clawdbotSkillplugin-sdk-impact
Count Plugin SDK consumers across live ClawHub releases and bundled OpenClaw plugins before deprecation, removal, or behavior changes; supports public release-date filters.
Also in 7 projects that use this
emanueleieloSkillsonos
Control Sonos speakers: discover, play/pause, volume, grouping, favorites, and queue management via sonos CLI.
Also in 5 projects that use this
- +2 more from molt-bot
Other versions100 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 100
- openclaw/openclaw★ 395ksame name
- moltbot/clawdbot★ 394ksame name
- steipete/warelay★ 394ksame name
- steipete/clawdis★ 394ksame name
- moltbot/moltbot★ 394ksame name
- clawdbot/clawdbot★ 394ksame name
- molt-bot/clawdbot★ 391ksame name
- NousResearch/hermes-agent★ 264ksame name
- spinabot/brigade★ 11ksame name
- steipete/agent-scripts★ 7.5ksame name
90 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 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-captureSkill
- obsidian-dailySkill
- obsidian-recapSkill
- obsidian-searchSkill
- 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
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 95 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
Ask the user one question: "What are you trying to do?"
- Distinctive: line 50
If the intent is ambiguous after one question, present the table above and ask which row fits.
“Common” is measured: kept by at least 6 in 10 of the 95 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 Help
The Obsidian skill family writes and reads Claude session context directly into
your Obsidian vault — captures, session logs, daily activity notes, and
search across everything Claude has logged. Every note written follows a
consistent folder layout under Claude/ so the vault stays clean and
navigable.
The five skills
| Skill | Use when |
/obsidian-brief | Loading project context before starting work — synthesizes recent notes without a search query (read-only, not persisted) |
/obsidian-recap | Writing a synthesized daily recap of the project's work to the vault (persisted) |
/obsidian-capture | Saving a note, decision, or thought to the vault right now |
/obsidian-daily | Viewing today's Claude activity note |
/obsidian-search | Finding past session logs or captures by keyword |
Session notes are written automatically by the Stop/SessionEnd hooks — there is no manual "log this session" command. To turn those raw session notes into a readable narrative, use
/obsidian-recap.
1. Identify intent
Ask the user one question: "What are you trying to do?"
Listen for these patterns:
- "brief", "catch me up", "context", "what have we been working on", "load context" →
/obsidian-brief - "recap", "daily recap", "wrap up the day", "summarize today", "end-of-day summary" →
/obsidian-recap - "capture", "save", "note", "jot", "quick note", "save this" →
/obsidian-capture - "today", "daily", "what did I do today", "daily note" →
/obsidian-daily - "find", "search", "look up", "what did I log about" →
/obsidian-search
2. Route and hand off
Once intent is clear, tell the user which skill handles it and invoke it. For
example: "That's a daily recap — starting /obsidian-recap now."
If the intent is ambiguous after one question, present the table above and ask which row fits.
Gotchas
- Do not attempt the operation yourself. This skill only identifies intent and routes. The other skills handle execution.
- "I want to do multiple things" — Route to the most urgent one first. Obsidian write operations on the same vault must not run in parallel; the daily note append has a single owner.
- OBSIDIAN_VAULT_PATH not set — If the user has not configured the vault
path, all five skills will detect this and prompt them to run
install.sh. Route to whichever skill the user intended — it will handle the missing env var gracefully.
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.

