vault-explorer
Use proactively when researching what the vault knows about a topic, before creating new notes, or when exploring existing knowledge and connections. Run in foreground — results inform the caller's next steps. Examples: <example> Context: User asks about a topic before creating
$ npx -y skills add AdrianV101/obsidian-pkm-plugin --agent claude-codeShips with vault-pkm. Installing the plugin gets this agent.
How it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Use proactively when researching what the vault knows about a topic, before creating new notes, or when exploring existing knowledge and connections. Run in foreground — results inform the caller's next steps. Examples: <example> Context: User asks about a topic before creating
Give Claude persistent, structured memory across conversations using your Obsidian vault. Read, write, search, and navigate your knowledge base — all from within Claude Code.
Repo: AdrianV101/obsidian-pkm-plugin
Other agents on vault-pkm.
- link-auditor
Use proactively in the background after creating or modifying multiple vault notes, or when asked about vault link health. Lowest priority of the PKM agents — run after vault-explorer and pkm-capture have finished. Examples: <example> Context: Several new notes were created
Open agent - pkm-capture
Use proactively in the background after completing significant work blocks, after git commits (triggered automatically by PreToolUse hook), or before session ends. Captures session work into the PKM vault: devlog entries, decisions, research findings, tasks, and bug
Open agent