Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
Use this skill when the user asks about their notes, ideas, projects, or knowledge base stored in Obsidian. Triggers include: "search my notes", "what do I have on X", "find my notes about", "look in my vault", "what did I write about", "show me notes tagged", "give me an overview of my vault", "read my note on", "what notes do I have about", "what happened in my call with", "summarise my meeting with", or any request to explore or retrieve personal notes and knowledge.
npx claudepluginhub moesamn/obsidian-claude-pluginHow this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian-claude-plugin:obsidian-vaultThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Before using any vault tools, verify the vault is accessible by calling
Loads Obsidian vault notes as conversational context when users request personal notes via phrases like 'check my notes about'. Scans MOCs, retrieves linked notes, limits to 15k chars.
Searches, creates, and manages notes in an Obsidian vault using wikilinks and index notes. Useful for finding, organizing, or adding notes with title-case naming and flat folder structure.
Manages Obsidian vaults: search, create, edit, move Markdown notes; handle YAML frontmatter, wikilinks, backlinks, daily notes, Zettelkasten setup, and sync via obsidian-cli.
Share bugs, ideas, or general feedback.
Before using any vault tools, verify the vault is accessible by calling
get_vault_overview. If it returns an error about OBSIDIAN_VAULT_PATH
not being set, tell the user:
"Your Obsidian vault path isn't configured yet. Go to the plugin settings and set
OBSIDIAN_VAULT_PATHto the full path of your vault folder, then restart Cowork."
Do not proceed until the vault is confirmed accessible.
Use the MCP tools provided by the obsidian-vault server:
get_vault_overview — call this first to confirm access and understand
the vault's shape (size, tags, date range).list_notes — list notes with optional tag filter and result limit.read_note — read the full content and metadata of a single note by
its relative path.search_notes — full-text search across all notes; returns match
counts and contextual snippets.list_tags — list every tag used in the vault with note counts.get_notes_by_tag — retrieve all notes that carry a given tag.search_notes for broad keyword questions ("what do I know about X",
"what happened in my call with Y").get_notes_by_tag when the user mentions a specific topic or category
that may be a tag.list_notes to browse recent activity or get a full list.read_note to deep-dive into a specific note by path.Notes are Markdown files. Common metadata patterns:
--- block at the top): may include title, tags,
date, aliases, status, or custom fields.#tagname written anywhere in the body.[[Note Title]] — mention these to the user when relevant.2025-03-14.md) — these are typically journal or meeting entries.The vault is personal. Treat its contents with discretion. Stay faithful to what the user actually wrote. When surfacing patterns or connections across notes, do so thoughtfully and highlight what is most actionable or relevant.