- name
SKILL.md
スキルファイルは公開元のリポジトリに置かれたままです。
コピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add Ar9av/obsidian-wiki --skill memory-bridge -a cursor -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add Ar9av/obsidian-wiki --skill memory-bridge -a claude-code -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add Ar9av/obsidian-wiki --skill memory-bridge -a codex -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add Ar9av/obsidian-wiki --skill memory-bridge -a grok -yコピーしたメッセージを Grok Bot のチャットで送信してください。Bot がこの SKILL.md を GitHub から取得し、すべての Bot が共有するスキルに追加します。
Install this skill: https://github.com/Ar9av/obsidian-wiki/tree/HEAD/skills/memory-bridge公開元より
You 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.
llm-wiki/SKILL.md (inline @name override → walk up CWD for .env → global config → prompt setup). This gives OBSIDIAN_VAULT_PATH.$OBSIDIAN_VAULT_PATH/.manifest.json — this is the source-of-truth for what tool produced what.$OBSIDIAN_VAULT_PATH/index.md for page titles and one-line descriptions.Parse the user's invocation to determine mode:
Recognized tool names: claude, codex, hermes, openclaw, copilot, pi, manual (hand-written), ingest (wiki-ingest documents).
Read .manifest.json. For each source entry, extract:
source_type — maps to tool name:
claude_conversation, claude_memory, claude_audit_log, claude_desktop_session → claudecodex_rollout, codex_index, codex_history → codexhermes_memory, hermes_session → hermesopenclaw_memory, openclaw_daily_note, openclaw_session, openclaw_dreams → openclawcopilot_session, copilot_checkpoint, copilot_transcript, copilot_memory_artifact → copilotpi_session → pidocument → ingestmanualpages_created and pages_updated — the wiki pages that came out of this sourceBuild a map:
tool_pages = {
"claude": set(pages created/updated by claude sources),
"codex": set(pages created/updated by codex sources),
...
}
A page can appear in multiple tools' sets if multiple tools contributed to it.
Filter tool_pages[<tool>] and present as a grouped list:
## Knowledge from <tool> (<N> pages)
### By category
- concepts/ — N pages
- entities/ — N pages
- skills/ — N pages
...
### Pages
| Page | Category | Tags | Last updated |
|------|----------|------|--------------|
| [[page-name]] | concept | tag1, tag2 | 2026-04-10 |
...
Read frontmatter for the listed pages (grep for ^(title|category|tags|updated):) — do not read full page bodies unless the user asks.
Within the filtered page set, run:
rg -l "<topic>" <pages in tool set>
Then grep section headers (^##) around matches to give context without full reads. Present results as a ranked list with the matching excerpt.
Compute:
only_in_a = tool_pages[a] − tool_pages[b]only_in_b = tool_pages[b] − tool_pages[a]shared = tool_pages[a] ∩ tool_pages[b]If no specific tools are given, compare all tools pairwise (limit to pairs with >0 overlap or unique pages to keep output concise).
Present:
## Memory Bridge Diff — <tool-a> vs <tool-b>
### Only in <tool-a> (<N> pages)
These concepts exist in your wiki from <tool-a> sessions but <tool-b> has never touched them.
<list with one-line descriptions from index.md>
### Only in <tool-b> (<N> pages)
<list>
### Shared (<N> pages)
Both tools have contributed to these pages.
<list — only show if ≤15; otherwise just the count>
### Notable gaps
<highlight the most interesting asymmetries — e.g. "codex has 12 pages on build tooling that claude has never seen">
Build a matrix showing every page and which tools have touched it. Cap at 50 rows; sort by number of contributing tools descending (most cross-tool pages first — these are the richest nodes).
| Page | claude | codex | hermes | copilot | pi |
|------|--------|-------|--------|---------|----|
| [[react-patterns]] | ✓ | ✓ | — | ✓ | — |
| [[rust-ownership]] | — | ✓ | — | — | ✓ |
After generating output, if the impl-validator skill is available in the current environment, spawn it as a subagent:
impl-validator check:
goal: "Browse/diff wiki knowledge by source tool and surface cross-tool blind spots"
artifacts: [the output you just generated]
checks:
- Did you correctly parse source_type from .manifest.json?
- Are page counts plausible (not 0 unless vault is empty)?
- Is the diff symmetric (a−b and b−a are disjoint)?
- Did you avoid reading full page bodies when not needed?
Apply any issues it surfaces before presenting output to the user.
Append to $OBSIDIAN_VAULT_PATH/log.md:
- [TIMESTAMP] MEMORY-BRIDGE mode=<browse|search|diff|map> tool=<tool> pages_shown=N
[[wikilinks]] for page references (or standard Markdown links if OBSIDIAN_LINK_FORMAT=markdown is set)..manifest.json is empty or missing, say so clearly and suggest running /wiki-history-ingest first.>
---name: memory-bridgedescription: >---# skills/memory-bridge/SKILL.mdよくある質問
公開元から skills/memory-bridge/SKILL.md をダウンロードするか、パスをコピーしてリポジトリを開いてください。PlugMCP はスキルを掲載するだけで、ファイルはホストしていません。
公開元は https://github.com/Ar9av/obsidian-wiki で管理しています。
Claude、Cursor、Codex、Grok Build は、公開元のリポジトリから追加した SKILL.md を読み込めます。Grok Bot は、チャットでスキルの GitHub フォルダーのリンクを送るとインストールします。