
Wiki Export
Export the Obsidian wiki graph to JSON, GraphML, Neo4j Cypher, Postgres/SQL, HTML, or...
Install
npx skills add Ar9av/obsidian-wiki --skill wiki-export -g -a claude-code -y- Repository
- Ar9av/obsidian-wiki3.6k
- Category
- Data and ML
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Export the Obsidian wiki graph to JSON, GraphML, Neo4j Cypher, Postgres/SQL, HTML, or OKF bundles. Use when transferring or visualizing wiki data in external tools; wiki-import handles the reverse direction.
Wiki Export, Knowledge Graph Export
You are exporting the wiki's wikilink graph to structured formats so it can be used in external tools (Gephi, Neo4j, custom scripts, browser visualization).
Before You Start
- Resolve config, follow the Config Resolution Protocol in
llm-wiki/SKILL.md(inline@nameoverride → walk up CWD for.env→ global config → prompt setup). This givesOBSIDIAN_VAULT_PATH - Confirm the vault has pages to export, if fewer than 5 pages exist, warn the user and stop
Project Filter (optional)
If the user's invocation includes a project name, e.g. /wiki-export prismor, "export the prismor project", "export project:security", activate project filter mode:
- Extract the project name from the argument or phrase. Normalise: lowercase, strip the word "project".
- Keep only pages where either condition holds:
- The page
idstarts withprojects/<name>/(path-based match) - The page's
tagsarray contains<name>(tag-based match)
- The page
- Drop any edge where either endpoint was excluded.
- Note the filter in the summary:
(filtered: project:<name>, X of Y pages) - Set
graph.graph.filter = "project:<name>"in the JSON output.
If both a project filter and a visibility filter are active, apply both (project filter first, then visibility filter on the remaining set).
Visibility Filter (optional)
By default, all pages are exported regardless of visibility tags. This preserves existing behavior.
If the user requests a filtered export, phrases like "public export", "user-facing export", "exclude internal", "no internal pages", activate visibility filtered mode:
- Build a blocked tag set:
{visibility/internal, visibility/pii} - Skip any page whose frontmatter tags contain a blocked tag when building the node list
- Skip any edge where either endpoint was excluded
- Note the filter in the summary:
(filtered: visibility/internal, visibility/pii excluded)
