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).
From obsidian-pkmnpx claudepluginhub adrianv101/obsidian-pkm-plugin --plugin obsidian-pkmThis skill uses the workspace's default tool permissions.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Understand what the vault already knows about a topic before creating new notes or doing research. Combines graph traversal with semantic search to find both explicit connections and hidden relationships.
When to use: Researching vault knowledge on a topic, finding related notes, exploring a topic area before writing.
Find the most relevant existing note for the topic:
vault_semantic_search({ query: "<topic>", limit: 5 })
If vault_semantic_search is unavailable (no OPENAI_API_KEY), use vault_search with key terms and vault_query by tags/type to locate a seed note.
Explore the structural neighborhood around the seed note:
vault_neighborhood({ path: "<seed-note-path>", depth: 2, direction: "both" })
This reveals the intentional knowledge structure — what someone explicitly linked. If the seed note has no links (new or isolated note), this is expected — rely on Step 3 results for connection discovery. If vault_neighborhood returns an error (e.g., 'File not found'), the seed note may have been deleted or the path misresolved — try the next-best result from Step 1, or verify with vault_search.
Search for conceptually related notes that may not be in the graph:
vault_semantic_search({ query: "<topic>", limit: 10 })
If vault_semantic_search is unavailable (no OPENAI_API_KEY), use vault_search with multiple keyword variations and vault_query with relevant tags.
Compare the graph results (step 2) with semantic results (step 3):
| Category | Meaning | Action |
|---|---|---|
| In graph AND semantic | Well-connected, established knowledge | No action needed |
| In graph but NOT semantic | Structurally linked but topically distant | May indicate weak/outdated link |
| In semantic but NOT graph | Missing links — conceptually related but unconnected | Highest-value findings — suggest linking |
Note: If Step 3 used vault_search/vault_query (no OPENAI_API_KEY), the gap analysis is less precise — text search misses conceptually related notes that use different terminology. Flag this reduced fidelity when presenting findings.
Return findings organized as: