wiki-export

Export an Obsidian vault's wikilink graph to JSON, GraphML, Cypher, and HTML.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wiki-export turns an Obsidian vault’s knowledge graph (wikilinks between pages) into structured outputs so you can analyze it or use it in external tooling instead of working only inside the vault.

Core Features & Use Cases

  • Graph exports for external tools: Produces graph.json (NetworkX node_link), graph.graphml (Gephi/Cytoscape), cypher.txt (Neo4j), and graph.html (interactive visualization).
  • Config-aware vault resolution: Follows the project’s configuration resolution protocol to determine the vault path from environment and prompt setup.
  • Optional privacy/visibility filtering: Supports a filtered mode to exclude pages tagged with visibility/internal and visibility/pii, and to remove edges connected to excluded pages.
  • Wikilink parsing into edges: Extracts [[wikilink]] references from page bodies, resolves them to node IDs, and captures edge confidence (e.g., inferred/ambiguous markers).

Quick Start

Run the wiki-export skill to export your vault’s wikilink graph into wiki-export/ at the vault root, including graph.json, graph.graphml, cypher.txt, and graph.html.

Frequently Asked Questions about wiki-export

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

FAQPage Schema
How do I export an Obsidian vault wikilink graph to Neo4j?

Exporting an Obsidian vault wikilink graph to Neo4j involves extracting page nodes and wikilink edges, then generating a cypher.txt script. This output lets you import your knowledge graph directly into Neo4j for analytics.

Can I convert Obsidian wikilinks to GraphML for Gephi or Cytoscape?

Converting Obsidian wikilinks to GraphML for Gephi or Cytoscape is supported. The process parses [[wikilink]] references into structured edges and writes a graph.graphml file for use in external graph tooling.

What is the best way to visualize an Obsidian knowledge graph outside the vault?

Visualizing an Obsidian knowledge graph externally is done by generating a standalone graph.html file. This interactive visualization is written alongside JSON and GraphML outputs in a wiki-export directory at the vault root.

Does the Obsidian graph export support filtering out private or internal pages?

Obsidian graph export supports filtering private or internal pages via an optional visibility-filtered mode. It excludes pages tagged with visibility/internal or visibility/pii and removes their connected edges from the final export artifacts.

How do I resolve the vault path when exporting an Obsidian wikilink graph?

Resolving the vault path when exporting an Obsidian wikilink graph uses a config-aware resolution protocol checking environment and prompt setup. This deterministic resolution ensures correct page globbing and exclusions before generating output files.

What format is the Obsidian graph exported in for NetworkX analysis?

The Obsidian graph is exported in JSON format using the NetworkX node_link structure for analysis. This graph.json file captures page nodes, wikilink edges, and community assignments by dominant tag for downstream Python analytics.