memory-bridge MCP 服务器 | PlugMCP

memory-bridge

Ar9av3.7kstars

Knowledge MemoryProductivityCollaboration

1---2name: memory-bridge3description: >4---56# skills/memory-bridge/SKILL.md

SKILL.mdAgent skill

Transport: File
Status: Listed

SKILL.md

Install

The skill file stays in the publisher's repository.

Paste the copied command in a terminal. It installs this SKILL.md into that agent.

shterminal

1npx skills add Ar9av/obsidian-wiki --skill memory-bridge -a cursor -y

Paste the copied command in a terminal. It installs this SKILL.md into that agent.

shterminal

1npx skills add Ar9av/obsidian-wiki --skill memory-bridge -a claude-code -y

Paste the copied command in a terminal. It installs this SKILL.md into that agent.

shterminal

1npx skills add Ar9av/obsidian-wiki --skill memory-bridge -a codex -y

Paste the copied command in a terminal. It installs this SKILL.md into that agent.

shterminal

1npx skills add Ar9av/obsidian-wiki --skill memory-bridge -a grok -y

Send the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.

txtGrok Bot chat

1Install this skill: https://github.com/Ar9av/obsidian-wiki/tree/HEAD/skills/memory-bridge

Download skill skills/memory-bridge/SKILL.md on GitHub

skills/memory-bridge/SKILL.mdMarkdown · UTF-8

Skill facts

Agent skill

File: skills/memory-bridge/SKILL.md
Publisher: Ar9av
Hosting

FAQ

Questions

From the publisher

SKILL.md

name: memory-bridge
description: Browse or compare wiki knowledge by originating AI tool. Use for cross-tool memory questions, tool-specific knowledge, or gap/diff analysis between Codex, Claude, Hermes, and other agents.

Memory Bridge — Cross-Tool Knowledge Browser

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.

Before You Start

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.
Read $OBSIDIAN_VAULT_PATH/.manifest.json — this is the source-of-truth for what tool produced what.
Read $OBSIDIAN_VAULT_PATH/index.md for page titles and one-line descriptions.

Commands

Parse the user's invocation to determine mode:

Invocation	Mode
`/memory-bridge <tool>`	Browse — list all wiki pages sourced from `<tool>`
`/memory-bridge <tool> "<topic>"`	Search — pages from `<tool>` that mention `<topic>`
`/memory-bridge diff`	Diff — pages unique to each tool; overlap; blind spots
`/memory-bridge diff <tool-a> <tool-b>`	Diff — compare two specific tools
`/memory-bridge map`	Map — full origin matrix: every page × every tool that touched it

Recognized tool names: claude, codex, hermes, openclaw, copilot, pi, manual (hand-written), ingest (wiki-ingest documents).

Step 1: Build the Source Map

tool_pages = {
  "claude": set(pages created/updated by claude sources),
  "codex":  set(pages created/updated by codex sources),
  ...
}

## 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 |
...

rg -l "<topic>" <pages in tool set>

## 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">

| Page | claude | codex | hermes | copilot | pi |
|------|--------|-------|--------|---------|----|
| [[react-patterns]] | ✓ | ✓ | — | ✓ | — |
| [[rust-ownership]] | — | ✓ | — | — | ✓ |

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?

- [TIMESTAMP] MEMORY-BRIDGE mode=<browse|search|diff|map> tool=<tool> pages_shown=N

memory-bridge

Install

Skill facts

Questions

How do I install memory-bridge?

Where does memory-bridge live?

Which agents can use memory-bridge?

SKILL.md

Memory Bridge — Cross-Tool Knowledge Browser

Before You Start

Commands

Step 1: Build the Source Map

Step 2: Execute the Mode

Browse Mode

Search Mode

Diff Mode

Map Mode

Step 3: Spawn impl-validator (if available)

Step 4: Log

Output Conventions