memory-bridge

Identify wiki page origins from .manifest.json provenance and frontmatter sources.

6|2|Updated May 11, 2026
One-click install
npx skills add https://github.com/pax-k/war-gov-uap-wiki --skill memory-bridge-pax-k
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-bridge
Source: https://github.com/pax-k/war-gov-uap-wiki/tree/main/.cursor/skills/memory-bridge
Command: npx skills add https://github.com/pax-k/war-gov-uap-wiki --skill memory-bridge-pax-k

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browse and compare wiki knowledge by which AI tool originally produced it, enabling provenance-aware navigation across a multi-tool knowledge graph.

Core Features & Use Cases

  • Inspect page origins via the .manifest.json provenance and page frontmatter sources to understand data lineage.
  • Filter and group pages by source tool to compare cross-tool coverage and identify gaps.
  • Navigate the wiki graph to surface cross-tool relationships and provenance context for decision-making.

Quick Start

Invoke memory-bridge with a tool name to browse pages produced by that tool, or run a diff to compare provenance across tools.

Frequently Asked Questions about memory-bridge

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

FAQPage Schema
How do I track Obsidian wiki page provenance across multiple AI tools?

Track Obsidian wiki page provenance by reading the .manifest.json file and page frontmatter sources to identify which AI tool originally produced each page. This enables provenance-aware navigation across a multi-tool knowledge graph.

What is cross-tool gap analysis in an Obsidian wiki graph?

Cross-tool gap analysis in an Obsidian wiki graph involves filtering and grouping pages by their source tool to compare coverage. It uses .manifest.json provenance data to identify which tools have generated content and where gaps exist.

How do I filter wiki pages by source tool using frontmatter?

Filter wiki pages by source tool by invoking memory-bridge with a specific tool name to browse pages produced by that tool. The Skill reads page frontmatter sources and .manifest.json provenance to group and render origin-aware views.

Can I compare provenance across different tools in an Obsidian vault?

Compare provenance across different tools in an Obsidian vault by running a diff to compare provenance across tools. The Skill requires access to the vault manifest, index, and page frontmatter to surface cross-tool relationships and context.

Do I need vault manifest access to browse wiki page origins?

Vault manifest access is required to browse wiki page origins because the Skill relies on the .manifest.json provenance and page frontmatter sources to render origin-aware views and navigate the wiki graph accurately.

What are the limitations of provenance audits for wiki pages?

Provenance audits for wiki pages are limited by the availability and accuracy of .manifest.json and frontmatter sources. If pages lack proper provenance metadata, the Skill cannot identify their origin tool or render complete origin-aware views.