memory-bridge

Map wiki page provenance across AI tools from manifest metadata.

Updated Apr 27, 2014
One-click install
npx skills add https://github.com/Nirajkashyap/nirajkashyap.github.io --skill memory-bridge-nirajkashyap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-bridge
Source: https://github.com/Nirajkashyap/nirajkashyap.github.io/tree/main/.agents/skills/memory-bridge
Command: npx skills add https://github.com/Nirajkashyap/nirajkashyap.github.io --skill memory-bridge-nirajkashyap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browse and compare wiki knowledge to identify provenance by which AI tool originally produced it. This skill surfaces metadata from the .manifest.json and page sources: frontmatter, enabling a navigable view of cross-tool knowledge.

Core Features & Use Cases

  • Browse wiki pages by source tool.
  • Diff pages across tools to reveal overlaps, gaps, and blind spots.
  • Map the complete origin matrix: pages vs tools and provenance.

Quick Start

Ask the AI to run /memory-bridge diff claude codex to compare which pages are unique to each tool and where they overlap.

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 produced by different AI tools to find knowledge gaps?

You can compare wiki pages across AI tools by running a diff command to reveal overlaps, gaps, and blind spots. This cross-tool comparison maps provenance by reading manifest metadata to show which pages are unique to each tool.

What is cross-tool provenance mapping for wiki pages?

Cross-tool provenance mapping identifies which AI tool originally produced wiki content by reading manifest and index files. It maps page sources to tools like Claude, Codex, and Copilot, surfacing metadata without parsing full page bodies unless explicitly requested.

Can I browse wiki knowledge by source tool without loading full page content?

Yes, you can browse wiki knowledge by source tool through metadata extraction. The system reads manifest and index files to map page ownership across tools, avoiding full page body parsing unless you explicitly request it.

How do I map the complete origin matrix of pages versus AI tools?

To map the complete origin matrix, use the map mode to visualize pages versus tools and provenance. This generates a navigable view of cross-tool knowledge by analyzing manifest metadata and page frontmatter.

Does this cross-tool wiki browser support manual sources alongside AI-generated pages?

Yes, the browser supports manual sources alongside AI tools like Claude, Codex, Hermes, Openclaw, and Copilot. It reads manifest and index files to determine page ownership and provenance across all supported source types.

What are the limitations of comparing wiki provenance across multiple AI tools?

The main limitation is that full page bodies are not parsed unless explicitly requested, restricting comparison to metadata and frontmatter. Provenance accuracy also depends on the completeness of the manifest and index files.