memory-bridge

1# Memory Bridge — Cross-Tool Knowledge Browser
2 
3You are helping the user browse and compare their Obsidian wiki knowledge filtered by which AI tool originally produced it. The wiki tracks source provenance in `.manifest.json` and page `sources:` frontmatter — this skill surfaces that metadata as a navigable view.
4 
5## Before You Start
6 
71. **Resolve config** — follow the Config Resolution Protocol in `llm-wiki/SKILL.md` (inline `@name` override → walk up CWD for `.env` → global config → prompt setup). This gives `OBSIDIAN_VAULT_PATH`.
82. Read `$OBSIDIAN_VAULT_PATH/.manifest.json` — this is the source-of-truth for what tool produced what.
93. Read `$OBSIDIAN_VAULT_PATH/index.md` for page titles and one-line descriptions.
10 
11## Commands
12 
13Parse the user's invocation to determine mode:
14 
15| Invocation | Mode |
16|---|---|
17| `/memory-bridge <tool>` | **Browse** — list all wiki pages sourced from `<tool>` |
18| `/memory-bridge <tool> "<topic>"` | **Search** — pages from `<tool>` that mention `<topic>` |
19| `/memory-bridge diff` | **Diff** — pages unique to each tool; overlap; blind spots |
20| `/memory-bridge diff <tool-a> <tool-b>` | **Diff** — compare two specific tools |
21| `/memory-bridge map` | **Map** — full origin matrix: every page × every tool that touched it |
22 
23Recognized tool names: `claude`, `codex`, `hermes`, `openclaw`, `copilot`, `pi`, `manual` (hand-written), `ingest` (wiki-ingest documents).
24 
25## Step 1: Build the Source Map
26 
27Read `.manifest.json`. For each source entry, extract:
28…