wiki-export

Export an Obsidian wiki wikilink graph to JSON, GraphML, Cypher, and interactive HTML formats.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/phm-aguiar/test_documentacao --skill wiki-export-phm-aguiar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wiki-export
Source: https://github.com/phm-aguiar/test_documentacao/tree/main/.claude/skills/wiki-export
Command: npx skills add https://github.com/phm-aguiar/test_documentacao --skill wiki-export-phm-aguiar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Knowledge stored in an Obsidian wiki is locked inside Markdown files and wikilinks, making it hard to analyze or visualize in external graph tools. This Skill converts the entire wiki's link structure into standard graph formats ready for Gephi, Neo4j, NetworkX, or a browser. ## Core Features & Use Cases - Multi-format export: Generates graph.json (NetworkX node_link), graph.graphml (Gephi/yEd/Cytoscape), cypher.txt (Neo4j MERGE statements), and graph.html (interactive vis.js visualization) in one run. - Typed relationship enrichment: Reads relationships: frontmatter blocks to upgrade plain wikilinks into typed edges like contradicts, extends, or derived_from. - Project and visibility filters: Export only a specific project's pages or exclude pages tagged visibility/internal or visibility/pii for safe public sharing. - Use Case: You maintain a research wiki and want to present its structure to stakeholders. Run the export, open graph.html in a browser for an interactive community-colored map, and load graph.graphml into Gephi for deeper layout analysis. ## Quick Start Ask the assistant to export the wiki graph, optionally naming a project or requesting a public-only export, for example: export the wiki graph for the prismor project excluding internal pages.

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 to Gephi or Neo4j?▼

Run the wiki export to generate graph.graphml for Gephi, yEd, or Cytoscape, and cypher.txt containing Neo4j MERGE statements loadable via cypher-shell. Both files are written to a wiki-export directory at the vault root alongside graph.json and graph.html.

How to visualize an Obsidian wikilink graph in a browser?▼

The export produces graph.html, a self-contained vis.js visualization with nodes colored by tag-based community and sized by degree. Open the file in any browser to explore the graph with a dark sidebar showing click details and a community legend.

Can I export only one project or exclude private pages from the graph?▼

Yes, pass a project name to keep only pages under that project path or tagged with it, and request a public export to skip pages tagged visibility/internal or visibility/pii. Both filters can be combined, with the project filter applied first.

Does the export preserve typed relationships between wiki pages?▼

Typed edges are read from each page's relationships frontmatter block and override plain wikilinks with types like contradicts, extends, or derived_from. They appear as labeled edges in GraphML, uppercase relationship types in Cypher, and colored labeled edges in the HTML view.

What happens to broken wikilinks during graph export?▼

Broken wikilinks pointing to pages that do not exist in the vault are skipped, so only edges between existing pages are exported. Re-running the export is safe because all four output files are overwritten each time.