wiki-graph-export

Export Obsidian vault content as MemoryLane constellation graph nodes and edges.

4|Updated May 9, 2026

Search Tags:#knowledge graph #obsidian #json schema #wikilinks #graph export #frontend data #layout computation

Ready to run

npx skills add https://github.com/itsmarsss/memento --skill wiki-graph-export

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wiki-graph-export
Source: https://github.com/itsmarsss/memento/tree/main/obsidian-wiki/.skills/wiki-graph-export
Command: npx skills add https://github.com/itsmarsss/memento --skill wiki-graph-export

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires networkx.

What problem does it solve?

This Skill exports your Obsidian vault into the exact nodes-and-edges JSON format the MemoryLane frontend needs, eliminating broken or outdated constellation visuals after new moments are ingested.

Core Features & Use Cases

Vault-to-Frontend graph export: Generates _meta/graph.json with the fixed schema required by the frontend constellation viewer.
Wikilink-based relationship wiring: Parses [[wikilinks]] (including |alias display text) and converts them into undirected graph edges.
Deterministic, stable layout: Computes a force-directed layout and seeds from any existing _meta/graph.json so positions don’t “swim” between refreshes.
Ingestion-aware filtering: Excludes files marked ingest_status: pending or ingest_status: failed to avoid rendering incomplete data.

Quick Start

Export the graph by running wiki-graph-export after you ingest a batch of moments or when the user says “refresh frontend data.”

Frequently Asked Questions about wiki-graph-export

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

FAQPage Schema

How do I export an Obsidian vault to a JSON knowledge graph?▼

You can export an Obsidian vault to a JSON knowledge graph by parsing frontmatter and extracting alias-aware wikilinks to generate a structured `graph.json` file of nodes and edges.

How do I parse Obsidian wikilinks into graph edges for layout computation?▼

Parsing Obsidian wikilinks into graph edges involves extracting `[[wikilinks]]` along with `|alias` display text, which are then converted into undirected edges for force-directed layout computation.

Does this graph export method support deterministic layout positioning?▼

Deterministic layout positioning is supported by computing a force-directed layout and seeding node positions from any existing `graph.json` file to prevent nodes from swimming between refreshes.

Can I filter incomplete data when exporting a knowledge graph from Obsidian?▼

Filtering incomplete data during knowledge graph export is possible by excluding files marked with `ingest_status: pending` or `ingest_status: failed` in their frontmatter.

Do I need networkx to compute the force-directed layout for Obsidian wikilinks?▼

You need the `networkx` dependency to perform the graph layout computation and relationship wiring required to structure the parsed Obsidian wikilinks into nodes and edges.