Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ar9av/memory-bridge
Browse and compare wiki knowledge by which AI tool originally produced it.
Passed 12 of 17 test cases with the skill, and 6 of 17 without it.
and 10 more in the full report
9 fixed7 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
After executing a search command `/memory-bridge codex "refactoring"`, where and in what format should the action audit trail be recorded?
| Checked | Without skill | With skill |
|---|---|---|
| Appends a log line to $OBSIDIAN_VAULT_PATH/log.md. | Missed | Passed |
| Log entry includes mode, tool name, timestamp, and pages shown. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
llm-wiki/SKILL.md (inline @name override → walk up CWD for .env → global config → prompt setup). This gives OBSIDIAN_VAULT_PATH.$OBSIDIAN_VAULT_PATH/.manifest.json — this is the source-of-truth for what tool produced what.$OBSIDIAN_VAULT_PATH/index.md for page titles and one-line descriptions.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).
Read .manifest.json. For each source entry, extract:
source_type — maps to tool name:
claude_conversation, claude_memory, claude_audit_log, claude_desktop_session → claudecodex_rollout, codex_index, codex_history → codexhermes_memory, hermes_session → hermesopenclaw_memory, openclaw_daily_note, openclaw_session, openclaw_dreams → openclawcopilot_session, copilot_checkpoint, copilot_transcript, copilot_memory_artifact → copilotpi_session → pidocument → ingestmanualpages_created and pages_updated — the wiki pages that came out of this sourceBuild a map:
test cases passed, vs 6 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.