Skip to content
SkillModel-led7,455 tokens in use

wiki-export

Exports an Obsidian wiki's wikilink graph to JSON, GraphML, Neo4j Cypher, Postgres SQL and an interactive HTML view, plus an optional OKF markdown bundle.

3,792 stars on the repository MIT LicenseAr9av/obsidian-wiki · skills/wiki-export
pip install obsidian-wiki
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing wiki-export costs

52tokens idle
7,455tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure25/25
  • Examples12/15
  • Output10/15
  • Size9/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity100
  • Maintenance100
  • Community60
  • Maturity28
  • Momentum40

wiki-export reads every page in a vault, builds a node and edge list from frontmatter, wikilinks and typed relationships, and writes the graph in several formats so external tools can use it.

One run produces graph.json, graph.graphml, cypher.txt, postgres.sql and a self-contained graph.html, grouped into communities by tag. An OKF bundle with full page bodies is available on request, and project and visibility filters narrow what is exported.

What You Get

  • graph.json in NetworkX node-link format for scripts and graph libraries
  • graph.graphml for Gephi, yEd and Cytoscape
  • cypher.txt with MERGE statements for Neo4j
  • postgres.sql with two tables and upsert statements
  • graph.html, an interactive view colored by community and sized by link count
  • An optional OKF bundle that keeps full page bodies for round trips through wiki-import

Common Use Cases

  • Opening a vault’s link structure in Gephi or Neo4j for analysis
  • Loading wiki pages and edges into Postgres for custom queries
  • Sharing a public graph of a project while leaving out internal and private pages

What Makes It Unique

It covers five graph formats and a markdown bundle from one node and edge list, and it keeps typed relationships such as contradicts as named edge types in every format. Project filters match by folder or tag, and a public-export phrase drops pages tagged internal or private along with their edges. Re-running overwrites the outputs, and the notes advise gitignoring the derived folder.

Under The Hood

The skill is instructions for the agent. It reads the vault’s markdown files and writes the export files into a wiki-export folder inside the vault. The generated graph.html loads the vis.js library from a CDN when you open it in a browser, and the Cypher and SQL files are meant for you to load yourself with cypher-shell or psql. The skill does not run those loaders, fetch web pages or call remote APIs.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers