メニュー
Use to retrieve from an Obsidian vault by combining its link graph/tags with semantic search: produce a candidate note set (obsidian CLI, or rg fallback) and feed it to local-rag's --allowlist. For writing notes, Bases, or Canvas, use kepano/obsidian-skills.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Use when creating or editing a plugin for a multi-host GitHub Copilot / APM / Claude Code marketplace — required manifests, the plugin.json ⇆ apm.yml mirroring rule, portable env-var and install conventions, component layout, and the catalog entry.
Use when every unit of a corpus must be accounted for rather than merely searched — auditing a document set, log archive, or file tree with provable coverage and gaps split into truly absent versus undecidable.
Use when searching source code: text/regex (ripgrep), structural/AST patterns (ast-grep, semgrep), symbol definitions/references/callers (LSP, GNU Global, ctags), when/why code changed (git history), structural rewrites (comby), or size/complexity (tokei, scc).
Use when searching non-code corpora: query JSON/YAML/config (jq, yq, gron), tabular data files (duckdb, sqlite-utils), or content inside PDFs/Office/archives (rga, pandoc, pdftotext).
Use when deciding WHERE a piece of guidance should live — always-on memory (CLAUDE.md / AGENTS.md), a path-scoped rule, an on-demand skill, a subagent, an MCP server, or a deterministic hook — and how to keep the always-on budget small.
Use for semantic search over a markdown corpus when keywords aren't enough (you know the meaning, not the exact words), or hybrid semantic plus lexical search when both meaning and exact terms matter. Index once, then query.
SOC 職業分類に基づく
| name | obsidian-rag-bridge |
| description | Use to retrieve from an Obsidian vault by combining its link graph/tags with semantic search: produce a candidate note set (obsidian CLI, or rg fallback) and feed it to local-rag's --allowlist. For writing notes, Bases, or Canvas, use kepano/obsidian-skills. |
| license | MIT |
| compatibility | Best with the official obsidian CLI (Obsidian running). Falls back to rg/fd over the vault. Pairs with the local-rag plugin. |
| metadata | {"author":"Mark Beacom","version":"0.1.0"} |
| allowed-tools | Bash(obsidian:*) Bash(rag:*) Bash(rg:*) Bash(rtk rg:*) Bash(fd:*) Read Glob Grep |
Compose Obsidian's graph with semantic search. The pattern: narrow to candidate
notes via the graph/tags, then rerank semantically with rag.
Preferred — official obsidian CLI (requires Obsidian running; see
obsidian help and https://help.obsidian.md/cli):
obsidian backlinks file="Project X" # notes linking to a note
obsidian search query="retry policy" # full-text candidates
obsidian tags # explore tags
Extract note paths from the output to feed step 2.
Fallback — rg/fd (Obsidian not running / no CLI). Operates on files
directly; note the limitations (won't resolve aliases or [[link#heading]]):
VAULT="${CONTEXT_KIT_OBSIDIAN_VAULT:-${CLAUDE_PLUGIN_OPTION_VAULT_PATH:-.}}"
rg -l '\[\[Project X' "$VAULT" # approx backlinks
rg -l '(^|\s)#decision' "$VAULT" # notes with a tag
fd -e md . "$VAULT" # all notes
If
rtkis installed,rtk rg -l …compacts output while keeping-lraw, so the piped note paths in step 2 stay intact.obsidianandragaren't rtk-wrapped — they pass through unchanged.
Pipe candidate paths into local-rag's allowlist:
obsidian backlinks file="Project X" | rag query "open risks and mitigations" --name notes --allowlist -
rg -l '(^|\s)#decision' "$VAULT" | rag query "why did we choose X" --name notes --allowlist -
(Index the vault first: rag index "$VAULT" --name notes.)
rag returns path > heading + snippet. Use rg to jump to the exact lines.
This plugin only bridges retrieval. For authoring Obsidian notes, Bases,
or Canvas, install kepano/obsidian-skills
(the Obsidian founder's MIT skills) and use the official obsidian CLI.