wiki-export
Export the Obsidian wiki's knowledge graph to structured formats for use in external tools. Use this skill when the user says "export wiki", "export graph", "export to JSON", "export to Gephi", "export to Neo4j", "export to Postgres", "export to SQL", "graphml", "visualize wiki", "knowledge graph export", "export to OKF", "OKF bundle", "open knowledge format", "export as markdown bundle", or wants to use their wiki data in another tool. Outputs graph.json, graph.graphml, cypher.txt (Neo4j), postgres.sql (Postgres), and graph.html (interactive browser visualization) into a wiki-export/ directory at the vault root, plus an optional OKF (Open Knowledge Format) markdown bundle under wiki-export/okf/.
Ar9av · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Ar9av/obsidian-wiki --skill wiki-export技能说明
name: wiki-export description: > Export the Obsidian wiki's knowledge graph to structured formats for use in external tools. Use this skill when the user says "export wiki", "export graph", "export to JSON", "export to Gephi", "export to Neo4j", "export to Postgres", "export to SQL", "graphml", "visualize wiki", "knowledge graph export", "export to OKF", "OKF bundle", "open knowledge format", "export as markdown bundle", or wants to use their wiki data in another tool. Outputs graph.json, graph.graphml, cypher.txt (Neo4j), postgres.sql (Postgres), and graph.html (interactive browser visualization) into a wiki-export/ directory at the vault root, plus an optional OKF (Open Knowledge Format) markdown bundle under wiki-export/okf/.
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)
Pages with no visibility/ tag, or tagged visibility/public, are always included.
Step 1: Build the Node and Edge Lists
Glob all .md files in the vault (excluding _archives/, _raw/, _readouts/, .obsidian/, index.md, log.md, _insights.md). Apply any active filters (project and/or visibility) after collecting the full file list.
For each page, extract from frontmatter:
id— relative path from vault root, without.mdextension (e.g.concepts/transformers)label—titlefield from frontmatter, or filename if missingcategory— directory prefix (concepts,entities,skills,references,synthesis,projects, orjournal)tags— array from frontmatter tags fieldsummary— frontmattersummaryfield if present
This is your node list.
For each page, Grep the body for \[\[.*?\]\] to extract all wikilinks:
- Parse each
[[target]]or[[target|display]]— use the target part only - Resolve the target to a node id (normalize: lowercase, spaces→hyphens, strip
.md) - Skip links that point outside the node list (broken links)
- Each resolved link becomes an edge:
{source: page_id, target: linked_id, relation: "wikilink", confidence: "EXTRACTED"} - If the linking sentence ends with
^[inferred]or^[ambiguous], overrideconfidenceaccordingly
Typed edge enrichment: After building the wikilink edge list, read each page's relationships: frontmatter block. For each {target, type} entry:
- The
targetYAML value is a quoted wikilink string such as"[[concepts/lstm]]". Strip the surrounding[[and]]characters, then apply the same normalization (lowercase, spaces→hyphens, strip.md) to get the node id. - Skip entries whose resolved target is not in the node list (broken link)
- If an edge for this
(source, target)pair already exists, override itsrelationfield with the typed value (e.g.,"contradicts") and settyped: true - If no edge exists yet for this pair, add one:
{source: page_id, target: target_id, relation: <type>, confidence: "EXTRACTED", typed: true}
This means relation: "wikilink" is the default for plain untyped links; a relationships: entry promotes it to a named semantic type. Edges that originated from both a body wikilink and a relationships: entry keep a single record — the typed version wins.
This is your edge list.
Step 2: Assign Community IDs
Group pages into communities by tag clustering:
- Pages sharing the same dominant tag belong to the same community
- Dominant tag = the first tag in the page's frontmatter tags array
- Pages with no tags get community id
null - Number communities starting from 0, ordered by size descending (largest community = 0)
This enables community-based coloring in the HTML visualization and tools like Gephi.
Step 3: Write the Output Files
Create wiki-export/ at the vault root if it doesn't exist. Write all five files:
3a. graph.json
NetworkX node_link format — standard for graph tools and scripts:
{
"directed": false,
"multigraph": false,
"graph": {
"exported_at": "<ISO timestamp>",
"vault": "<OBSIDIAN_VAULT_PATH>",
"total_nodes": N,
"total_edges": M
},
"nodes": [
{
阅读完整来源 ↗