vault-pkm

Configure this project for Obsidian PKM — connects the repo to a vault project folder and writes CLAUDE.md integration directives

Configure Vault PKM plugin — set vault path, API keys, and verify setup

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 during a research session. user: "OK I think we've captured everything from that research" assistant: "I'll run link-auditor in the background to check the new notes are well-connected." <commentary> Multiple notes created — audit link health to catch orphans and missing connections. </commentary> </example> <example> Context: User asks about vault health. user: "How healthy are the links in the vault?" assistant: "I'll delegate to link-auditor to run a comprehensive health check." <commentary> Explicit request for link health analysis. </commentary> </example>

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 documentation. Conservative — most exchanges produce nothing worth capturing beyond the devlog entry. When delegating, include: (1) whether this is the first capture this session or a subsequent one, (2) if subsequent, the timestamp of the previous devlog entry, (3) the project's vault path. Examples: <example> Context: A significant chunk of feature work has been completed. user: "OK, that feature is done. Let's move on to the next thing." assistant: "I'll dispatch pkm-capture in the background to record this work before we continue." <commentary> End of a development block — proactively capture without blocking. </commentary> </example> <example> Context: User is wrapping up for the day. user: "I think that's it for today" assistant: "Let me run pkm-capture in the background to capture today's session before we wrap up." <commentary> Session end — ensure work is documented. </commentary> </example> <example> Context: A significant architecture decision was made during implementation. user: "Great, let's go with the event-sourcing approach for the audit log" assistant: "I'll dispatch pkm-capture in the background to capture that architecture decision." <commentary> An architecture decision was agreed upon — worth capturing as an ADR. </commentary> </example> <example> Context: A complex debugging session revealed a non-obvious root cause. user: "Ah, so the race condition was caused by the connection pool timeout" assistant: "Good find. I'll run pkm-capture to capture this debugging insight." <commentary> Complex bug root cause — worth preserving as a troubleshooting log. </commentary> </example> <example> Context: Research produced a reusable insight about a technology. user: "Interesting, so sqlite-vec handles concurrent reads but not writes" assistant: "I'll have pkm-capture capture that finding in the background." <commentary> Research finding about a technology — reusable knowledge worth documenting. </commentary> </example>

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 new content. user: "What does the vault already know about caching strategies?" assistant: "I'll use the vault-explorer agent to research the vault's existing knowledge on caching." <commentary> Vault exploration before note creation prevents duplicates and discovers connections. </commentary> </example> <example> Context: User wants to understand knowledge coverage in an area. user: "Show me what we have documented about authentication" assistant: "I'll delegate to vault-explorer to map out the authentication knowledge in the vault." <commentary> Deep vault research benefits from isolated context and focused tool access. </commentary> </example> <example> Context: Planning new feature work and wanting to check existing research. user: "Before we start on the API redesign, what research do we already have?" assistant: "Let me use vault-explorer to find all related research and decisions." <commentary> Proactive exploration before significant work blocks. </commentary> </example>

Use when you want to quickly capture a new task in the vault from a title, with optional priority and due date.

Use when researching what the vault knows about a topic — performs graph + semantic exploration with gap analysis to map existing knowledge and find missing connections. Primarily used via the vault-explorer agent. Not for routine session-start context loading (hooks handle that).

Use when wrapping up a work session — creates devlog entry, captures undocumented decisions/research/debugging, audits link health of session work, and updates project index. Primarily used via the pkm-capture agent.

Use when writing to the vault — creating new notes (vault_write), editing existing notes (vault_edit, vault_append, vault_update_frontmatter). Handles duplicate checking, link discovery, annotations, and index updates for new notes. Provides guidelines for modifications.

Use when starting work on a specific vault task, when a task title or path is mentioned, or when coming from triage output.

2 hooks across 2 events