Agent skill

Memory Bridge

Browse or compare wiki knowledge by originating AI tool. An agent skill from Ar9av/obsidian-wiki.

MITAuto-check: notesKnowledge Management

Install Memory Bridge

skills CLI

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

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Ar9av/obsidian-wiki memory-bridge --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.skills/memory-bridge .claude/skills/memory-bridge && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "memory-bridge" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/memory-bridge into .claude/skills/memory-bridge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-bridge", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/memory-bridge

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

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

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Ar9av/obsidian-wiki memory-bridge --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.skills/memory-bridge .agents/skills/memory-bridge && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "memory-bridge" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/memory-bridge into .agents/skills/memory-bridge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-bridge", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

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

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Ar9av/obsidian-wiki memory-bridge --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.skills/memory-bridge .cursor/skills/memory-bridge && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "memory-bridge" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/memory-bridge into .cursor/skills/memory-bridge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-bridge", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Ar9av/obsidian-wiki.git --path .skills/memory-bridge

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Ar9av/obsidian-wiki --skill memory-bridge -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Ar9av/obsidian-wiki memory-bridge --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.skills/memory-bridge .gemini/skills/memory-bridge && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "memory-bridge" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/memory-bridge into .gemini/skills/memory-bridge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-bridge", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Ar9av/obsidian-wiki memory-bridge

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Ar9av/obsidian-wiki --skill memory-bridge -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .github/skills && cp -r skills-src/.skills/memory-bridge .github/skills/memory-bridge && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "memory-bridge" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/memory-bridge into .github/skills/memory-bridge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-bridge", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Ar9av/obsidian-wiki --skill memory-bridge -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Ar9av/obsidian-wiki memory-bridge --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.skills/memory-bridge .opencode/skills/memory-bridge && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "memory-bridge" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/memory-bridge into .opencode/skills/memory-bridge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-bridge", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: memory-bridge
GitHub stars: 3.5k
Used in: 1 other repo
Token cost: ~1.5k tokens
SKILL.md length: 485 words
Files: 1
Skills in repo: 39
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Browse or compare wiki knowledge by originating AI tool. An agent skill from Ar9av/obsidian-wiki.

Works in 4 steps: Build the Source Map → Execute the Mode → Spawn impl-validator (if available) → …
Cross-tool memory questions
SKILL.md covers Before You Start, Commands, Step 1: Build the Source Map and Step 2: Execute the Mode, plus 3 more sections
Calls rg, claude and codex

What it does

Memory Bridge is an agent skill from Ar9av/obsidian-wiki. 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.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Knowledge Management, covering LLM wikis. It works with Obsidian. The repository describes itself as: Framework for AI agents to build and maintain a digital brain through Obsidian wiki | Memory System for Agents. The licence is MIT.

When your agent uses it

Cross-tool memory questions
Tool-specific knowledge
Gap/diff analysis between Codex

Example prompts

“/memory-bridge”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Build the Source Map
Execute the Mode
Spawn impl-validator (if available)
Log

What it can do on your machine

Read from SKILL.md and the folder at commit 709727e. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- rg
- claude
- codex
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Memory Bridge loads about 1.5k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 485 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~51
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:13

line `@name` override → walk up CWD for `.env` → global config → prompt setup). This gives `OBSIDIAN_VAULT_PATH`.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Ar9av/obsidian-wiki at commit 709727e, republished under its MIT licence (© Ar9av). 485 words, ~1,464 tokens.

Download SKILL.mdSave it as .claude/skills/memory-bridge/SKILL.md (or your agent's skills folder).

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

Read .manifest.json. For each source entry, extract:

source_type — maps to tool name:
- claude_conversation, claude_memory, claude_audit_log, claude_desktop_session → claude
- codex_rollout, codex_index, codex_history → codex
- hermes_memory, hermes_session → hermes
- openclaw_memory, openclaw_daily_note, openclaw_session, openclaw_dreams → openclaw
- copilot_session, copilot_checkpoint, copilot_transcript, copilot_memory_artifact → copilot
- pi_session → pi
- document → ingest
- anything else → manual
pages_created and pages_updated — the wiki pages that came out of this source

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

Step 2: Execute the Mode

Browse Mode

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.

Show full SKILL.md (204 more words)Show less

Search Mode

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.

Diff Mode

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

Map Mode

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]] | — | ✓ | — | — | ✓ |

Step 3: Spawn impl-validator (if available)

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.

Step 4: Log

Append to $OBSIDIAN_VAULT_PATH/log.md:

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

Output Conventions

Always show page counts so the user can calibrate how much knowledge is in each tool's silo.
Use [[wikilinks]] for page references (or standard Markdown links if OBSIDIAN_LINK_FORMAT=markdown is set).
In diff mode, call out the most surprising asymmetry explicitly — that's the insight the user came for.
If .manifest.json is empty or missing, say so clearly and suggest running /wiki-history-ingest first.

Files

Just SKILL.md in .skills/memory-bridge of Ar9av/obsidian-wiki.

Open the folder on GitHubat commit 709727e

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Ar9av/obsidian-wiki, which our catalogue first saw on October 7, 2026.

majiayu000/claude-skill-registryskills/ai-llm/memory-bridge

Compare with similar skills

Memory Bridge next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Memory Bridge compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Memory Bridge this skillAr9av/obsidian-wiki	3.5k	1 repos	~1.5k	Automated safety check: Notes	MIT	today
LLM Wikilewislulu/llm-wiki-skill	655	—	~3.7k	Automated safety check: Pass	None	5 mo ago
Obsidian CLI Read TransportAgriciDaniel/claude-obsidian	15k	1 repos	~762	Automated safety check: Pass	MIT	27 days ago
LLM Wikizosmaai/pi-llm-wiki	606	—	~4.4k	Automated safety check: Pass	MIT	yesterday
LLM Wikipraneybehl/llm-wiki-plugin	118	—	~5.7k	Automated safety check: Pass	MIT	25 days ago
Karpathy WikiSherwinQ/karpathy-wiki	113	—	~967	Automated safety check: Pass	MIT	5 mo ago

Similar skills

LLM Wiki
lewislulu/llm-wiki-skill
Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers…
655 GitHub stars~3.7k tokensUpdated 5 mo ago
Knowledge ManagementAuto-check passed
Obsidian CLI Read Transport
AgriciDaniel/claude-obsidian
Detects and uses the official Obsidian command-line interface for read-only vault access, falling back to direct file reads, while all mutations stay on a separate transaction core.
15k GitHub starsUsed in 1 repo~762 tokens
Knowledge ManagementAuto-check passed
LLM Wiki
zosmaai/pi-llm-wiki
Build and maintain a persistent, interlinked Obsidian-compatible markdown wiki using Karpathy's LLM Wiki pattern.
606 GitHub stars~4.4k tokensUpdated yesterday
Knowledge ManagementAuto-check passed
LLM Wiki
praneybehl/llm-wiki-plugin
Build and maintain an LLM-curated knowledge base from papers, articles, transcripts, notes and project findings.
118 GitHub stars~5.7k tokensUpdated 25 days ago
Knowledge ManagementAuto-check passed
Karpathy Wiki
SherwinQ/karpathy-wiki
A skill your agent uses when building or maintaining a personal knowledge base with LLM assistance.
113 GitHub stars~967 tokensUpdated 5 mo ago
Knowledge ManagementAuto-check passed
My LLM Wiki
MartinLwx/dotfiles
Provides access to the user's personal wiki, including notes, research, project documentation, decisions, and archived knowledge.
140 GitHub stars~2.7k tokensUpdated 18 days ago
Knowledge ManagementAuto-check passed

Questions about Memory Bridge

What does Memory Bridge do?

Browse or compare wiki knowledge by originating AI tool. An agent skill from Ar9av/obsidian-wiki. Memory Bridge is an agent skill from Ar9av/obsidian-wiki. Browse or compare wiki knowledge by originating AI tool.

When should I use Memory Bridge?

Memory Bridge fits situations like: cross-tool memory questions; tool-specific knowledge; gap/diff analysis between Codex.

How do I install Memory Bridge in Claude Code?

Run `npx skills add Ar9av/obsidian-wiki --skill memory-bridge -a claude-code`. Or copy the skill folder (.skills/memory-bridge in Ar9av/obsidian-wiki) into .claude/skills/memory-bridge in your project. Claude Code loads it when a task matches its description.

How do I install Memory Bridge in Codex?

Run `npx skills add Ar9av/obsidian-wiki --skill memory-bridge -a codex`. Or copy the skill folder (.skills/memory-bridge in Ar9av/obsidian-wiki) into .agents/skills/memory-bridge in your project. Codex loads it when a task matches its description.

Can I use Memory Bridge in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Ar9av/obsidian-wiki --skill memory-bridge -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/memory-bridge, .gemini/skills/memory-bridge, .github/skills/memory-bridge and .opencode/skills/memory-bridge in your project.

What does Memory Bridge need to run?

Going by SKILL.md and its folder, Memory Bridge needs the command-line tools its instructions call (rg, claude and codex).

Does Memory Bridge access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Memory Bridge safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Memory Bridge use?

Memory Bridge is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Memory Bridge use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Memory Bridge?

Skills that share tags, products or a category with Memory Bridge: LLM Wiki (lewislulu/llm-wiki-skill, 655 stars), Obsidian CLI Read Transport (AgriciDaniel/claude-obsidian, 15k stars), LLM Wiki (zosmaai/pi-llm-wiki, 606 stars) and LLM Wiki (praneybehl/llm-wiki-plugin, 118 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Memory Bridge?

Ar9av (a GitHub user) maintains it in Ar9av/obsidian-wiki, which has 3,532 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 7, 2026.

Source: Ar9av/obsidian-wiki on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Memory Bridge

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

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

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from Ar9av/obsidian-wiki

Related

Questions about Memory Bridge