memory-bridge

Compare Obsidian wiki pages by AI tool provenance using browser, diff, and map modes.

Updated Feb 2, 2016
One-click install
npx skills add https://github.com/zjykzk/blog --skill memory-bridge-zjykzk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-bridge
Source: https://github.com/zjykzk/blog/tree/main/.agents/skills/memory-bridge
Command: npx skills add https://github.com/zjykzk/blog --skill memory-bridge-zjykzk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browse and compare wiki knowledge by provenance — surface which AI tool originally produced each page and expose cross-tool blind spots.

Core Features & Use Cases

  • Cross-tool provenance browsing: filter pages by source tool and view their origins.
  • Diff & map modes: identify pages unique to a tool, shared pages, and the complete origin matrix.
  • Gap analysis workflow: audit wiki coverage across tools to surface blind spots.

Quick Start

Invoke memory-bridge with a tool name (e.g., claude) to list wiki pages by origin and start exploring provenance.

Frequently Asked Questions about memory-bridge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I compare wiki pages across different AI tools in Obsidian?

To compare wiki pages across AI tools in Obsidian, this Skill reads .manifest.json and page frontmatter to build an origin map, applying diff and map modes to surface cross-tool gaps and overlaps.

What is wiki provenance and how does it help with gap analysis?

Wiki provenance identifies the originating AI tool for each page, helping you perform gap analysis by exposing cross-tool blind spots. It allows you to audit wiki coverage to see which tools generated unique content and which share overlapping knowledge.

How do I find Obsidian pages generated by a specific AI tool?

To find Obsidian pages generated by a specific AI tool, invoke the browser mode with the tool name, such as claude. The Skill reads the .manifest.json metadata to list wiki pages by their origin and renders a navigable view for exploration.

Do I need a .manifest.json file to track cross-tool wiki origins?

Yes, a .manifest.json file is required to track cross-tool wiki origins. The Skill relies on reading .manifest.json alongside page frontmatter to build the origin matrix and accurately map which AI tool originally produced each wiki page.

What is the best way to audit knowledge coverage across multiple AI tools?

The best way to audit knowledge coverage across AI tools is using the diff and map modes to identify unique and shared pages. This approach surfaces blind spots by rendering a complete origin matrix from your wiki metadata.

Can I view a complete origin matrix for all my Obsidian wiki pages?

Yes, you can view a complete origin matrix for your Obsidian wiki pages. The Skill applies map mode to read .manifest.json and frontmatter, rendering a navigable view that shows exactly which AI tool produced each page and where overlaps occur.