wiki-evidence

Convert Obsidian markdown pages into MemoryLane evidence-sheet JSON with wikilink resolution.

4|Updated May 9, 2026
One-click install
npx skills add https://github.com/itsmarsss/memento --skill wiki-evidence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-evidence
Source: https://github.com/itsmarsss/memento/tree/main/obsidian-wiki/.skills/wiki-evidence
Command: npx skills add https://github.com/itsmarsss/memento --skill wiki-evidence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts an Obsidian vault page (moment, entity, session, or synthesis) into the exact JSON structure the MemoryLane evidence sheet expects, eliminating manual formatting and mismatched schemas.

Core Features & Use Cases

  • Per-block typed JSON output: Turns markdown into ordered blocks (h1, h2, paragraphs, blockquotes, and link lists) matching the frontend’s renderer.
  • Frontmatter passthrough: Preserves YAML keys and values verbatim so the UI can display the page metadata accurately.
  • Wikilink resolution to connected node ids: Resolves [[wikilinks]] into connected graph node IDs using _meta/graph.json (or falls back to vault scanning) and returns a deduplicated, alphabetically sorted connected[] list.
  • Backend-oriented machine output: Emits compact, stdout-only JSON for automated routes like /api/evidence/{block_id} rather than conversational chat.

Quick Start

Run the skill with the block id you want to inspect: wiki-evidence <block_id>.

Frequently Asked Questions about wiki-evidence

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

FAQPage Schema
How do I convert Obsidian vault markdown pages into JSON for frontend rendering?

Converting Obsidian vault markdown pages into JSON involves resolving YAML frontmatter, tokenizing the body into typed blocks, and mapping wikilinks to connected node ids to produce deterministic evidence-sheet JSON for frontend renderers.

How do I extract YAML frontmatter and wikilinks from markdown to build a knowledge graph?

Extracting YAML frontmatter preserves metadata verbatim, while alias-aware wikilink parsing resolves links into connected graph node ids using a graph file or vault scanning, outputting a deduplicated, alphabetically sorted connected list.

Can I use Obsidian wikilinks to generate structured JSON for an API endpoint?

Yes, resolving Obsidian wikilinks into evidence JSON emits compact, stdout-only output designed for automated API routes, returning structured block data and connected node relationships rather than conversational chat.

What is the best way to tokenize markdown body content into typed blocks for evidence rendering?

Tokenizing markdown body content into typed blocks parses elements like h1, h2, paragraphs, and blockquotes into ordered JSON structures, matching the frontend renderer's expectations for moments, people, and places.

Does the evidence JSON output support different node types like sessions and synthesis pages?

Evidence JSON output applies to rendering moments, people, places, objects, sessions, and synthesis pages via block_id lookups, optionally guided by a node_type hint to ensure accurate schema mapping.

Why does my markdown to JSON conversion fail to match the expected frontend schema?

Markdown to JSON conversion requires deterministic output with a fixed schema, ensuring stable connected node sorting and failure responses that emit only JSON to stdout to prevent frontend rendering mismatches.