SkillAgentSearch skills...

wiki-import

Import a wiki graph into the current vault from graph.json or an OKF/markdown bundle. Use for transferring previously exported wiki content between vaults; pair with wiki-export for the reverse direction.

Install / Use

npx skills add Ar9av/obsidian-wiki --skill wiki-import

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

95/100

Supported Platforms

Universal

Tags

Our assessment of wiki-import

wiki-import scores 95/100 on our quality scale, 128th of 1,155 Content & Media skills we index (top 12%).

Its SKILL.md is 16 KB long, well organised into 16 sections with 9 code examples: a thorough specification that gives an agent plenty to work with.

With 3,485 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so wiki-import is actively maintained.
  • Our last check on 2026-11-16 could not reach the source (HTTP 404); it may have been moved or deleted.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

wiki-import compared with similar skills

All 4 of these similar skills score higher than wiki-import; compare them before choosing.

SkillScoreStarsUpdatedFormat
wiki-import (this skill)by Ar9av953.5k54d agoSKILL.md
siyuanby siyuan-note10047.3ktodayMCP Server
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install wiki-import?
Run npx skills add Ar9av/obsidian-wiki --skill wiki-import. The install tabs above show the steps for each supported agent.
Which AI agents does wiki-import work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is wiki-import safe to use?
It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is wiki-import still maintained?
The repository was last updated about 2 months ago, so wiki-import is actively maintained.

name: wiki-import description: > Import a wiki graph into the current vault from graph.json or an OKF/markdown bundle. Use for transferring previously exported wiki content between vaults; pair with wiki-export for the reverse direction.

Wiki Import — Reconstruct Pages from an Export

You are importing a vault's knowledge into the current vault from one of two sources produced by wiki-export:

  • graph.json — the graph skeleton. Reconstructs page stubs (frontmatter, typed relationships, a ## Related link list — no body). Lossy.
  • OKF bundle (a wiki-export/okf/ directory) — the actual markdown files. Reconstructs full pages with their real bodies. Lossless. Use this for true vault-to-vault transfer.

Either way, the import writes pages with correct frontmatter and wikilinks, then updates all vault metadata. Step 2, Step 3 (graph only), and Step 5 are shared; Step 4 forks by source type.

Before You Start

Writing profile: Before drafting or rewriting natural-language Markdown, read and apply the Writing Profile Resolution section in llm-wiki/SKILL.md. Framework schema, provenance, safety, and operation-specific requirements take precedence. Preserve imported source prose; apply WRITING.md preferences only to newly generated metadata or stubs.

  1. Resolve config — follow the Config Resolution Protocol in llm-wiki/SKILL.md (inline @name override → walk up CWD for .env → global config → prompt setup). This gives OBSIDIAN_VAULT_PATH.
  2. Read $OBSIDIAN_VAULT_PATH/AGENTS.md if it exists — apply any owner-specific conventions.

Step 1: Locate and Detect Source Type

Find the import source:

  • If the user provided a path argument, use it directly.
  • Otherwise auto-detect, in order: ./wiki-export/okf/ (a directory) → ./wiki-export/graph.json (a file).
  • If neither exists, ask the user for the path.

Detect the source type:

  • The path is a file ending in .json → graph.json import (validate below, then Step 3 + Step 4-Graph).
  • The path is a directory containing .md files with OKF frontmatter (a type: key), and/or a root index.md with okf_version → OKF bundle import (skip Step 3; go to Step 4-OKF). Both okf_version 0.1 and 0.2 bundles are accepted; Step 4-OKF reads either.
  • Anything else → report what's wrong and stop.

Validate a graph.json source:

  • Must be valid JSON
  • Must have top-level keys: nodes (array), links (array), graph (object)
  • Must have at least 1 node

If validation fails, report what's wrong and stop.

Validate an OKF bundle source:

  • Must contain at least 1 non-reserved .md file (i.e. not index.md/log.md) with parseable YAML frontmatter containing a non-empty type.
  • A .md with no frontmatter or no type is skipped (with a count), not fatal — OKF consumers are permissive (OKF §11).

Show a preview before importing:

graph.json:

Import preview (graph.json — stubs)
  Source: <path>  (exported at <graph.exported_at>)
  Nodes:  N total  (concepts: A, entities: B, skills: C, references: D, ...)
  Links:  M edges  (X typed, Y untyped)
  Target: $OBSIDIAN_VAULT_PATH

OKF bundle:

Import preview (OKF bundle — full pages)
  Source: <dir>  (okf_version <ver if present>)
  Pages:  N total  (concepts: A, entities: B, skills: C, references: D, ...)
  Target: $OBSIDIAN_VAULT_PATH

Step 2: Determine Conflict Resolution Mode

Read the user's phrasing to determine mode. Default is merge.

| Mode | Trigger phrases | Behaviour | |---|---|---| | merge | (default, no special phrasing) | Existing pages: update frontmatter tags/summary/relationships and add missing wikilinks; new pages: create stub. | | skip | "skip existing", "don't overwrite", "only new pages" | Leave existing pages completely untouched; only create pages that don't exist yet. | | overwrite | "overwrite", "replace existing", "force import" | Replace all matched pages with freshly reconstructed stubs regardless of existing content. |

Step 3: Build Internal Maps (graph.json only — skip for OKF bundles)

Before writing anything, build two maps from the links array:

Adjacency map — for each node id, collect all neighbour ids (edges in either direction):

adjacency["concepts/transformers"] = ["entities/vaswani", "concepts/lstm", ...]

Typed edge map — for each node id, collect outgoing typed edges only (typed: true):

typed_edges["concepts/transformers"] = [
  {target: "concepts/lstm", relation: "contradicts"},
  ...
]

Step 4-Graph: Reconstruct Pages from graph.json (graph.json source only)

Record counts: created = 0, skipped = 0, merged = 0.

For each node in nodes:

  1. Compute page_path = $VAULT/<node.id>.md
  2. Ensure the parent directory exists (e.g. $VAULT/concepts/)
  3. Check if the file already exists:
    • merge mode (default) + exists → read existing file, apply merge logic (see below), increment merged
    • merge mode (default) + doesn't exist → proceed to create stub, increment created
    • skip mode + exists → increment skipped, continue to next node
    • skip mode + doesn't exist → proceed to create stub, increment created
    • overwrite mode + exists → proceed to write fresh stub (overwrite), increment merged
    • overwrite mode + doesn't exist → proceed to create stub, increment created

Page template (new or overwrite)

---
title: <node.label>
category: <node.category>
tags: <node.tags as YAML list>
sources:
  - "imported from <graph.json path>"
<if node.summary exists>
summary: "<node.summary>"
</if>
<if typed_edges[node.id] is non-empty>
relationships:
<for each {target, relation} in typed_edges[node.id]>
  - target: "[[<target>]]"
    type: <relation>
</for>
</if>
lifecycle: draft
lifecycle_changed: <today YYYY-MM-DD>
base_confidence: 0.5
tier: supporting
created: <ISO timestamp>
updated: <ISO timestamp>
---

# <node.label>

<node.summary paragraph if available, else omit>

## Related

<for each neighbour in adjacency[node.id], sorted alphabetically>
<if edge is typed>
- [[<neighbour>]] — <relation>
<else>
- [[<neighbour>]]
</if>
</for>

If adjacency[node.id] is empty, omit the ## Related section entirely.

Merge logic (merge mode, existing page)

  1. Read the existing page's frontmatter.
  2. Tags: union of existing tags and node.tags (deduplicated, keep existing order, append new ones).
  3. Summary: if the existing page has no summary field and node.summary exists, add it.
  4. Relationships: union of existing relationships: entries and typed_edges[node.id] — skip entries where the same (target, type) pair already exists.
  5. Updated: set updated to the current ISO timestamp.
  6. Body: scan for a ## Related section. If it exists, append any missing wikilinks from adjacency[node.id] that aren't already linked anywhere in the body. If no ## Related section exists, append one with the missing links.
  7. Leave the rest of the body untouched.

Step 4-OKF: Reconstruct Pages from an OKF bundle (OKF source only)

Record counts: created = 0, skipped = 0, merged = 0, unparseable = 0.

Walk the bundle directory tree. For each .md file that is not a reserved file (index.md, log.md):

  1. Parse the YAML frontmatter. If it has no frontmatter or no non-empty type, increment unparseable and skip the file.
  2. Compute the concept id = the file's path relative to the bundle root, with .md stripped (e.g. concepts/transformers.md → concepts/transformers). The target page is $VAULT/<concept-id>.md.
  3. Reverse-map frontmatter (the inverse of the canonical mapping table in wiki-export Step 3.5):
    • title ← title.
    • category ← the preserved category extension key if present; else lower-case the directory prefix of the concept id (concepts/… → concepts); else derive from type (Concept→concepts, Entity→entities, Skill→skills, Reference→references, Synthesis→synthesis, Project→projects, Journal→journal).
    • tags ← tags.
    • summary ← description.
    • updated ← the preserved updated extension key if present; else generated.at; else a legacy v0.1 timestamp; else now.
    • created ← the preserved created extension key if present, else now.
    • sources ← OKF sources, as a list of strings: for each entry that is a mapping, take its resource; keep plain strings as-is (that's how v0.1 bundles from older exports carried our native list). If the bundle has no sources, use ["imported from OKF bundle <bundle path>"]. If a top-level resource URL is present and not already in the list, add it.
    • lifecycle ← the preserved lifecycle extension key if present; else from status: draft → draft, deprecated → archived, stable or absent → leave lifecycle unset. (OKF has no equivalent of reviewed/verified/disputed, so only our own exports restore them, through the preserved key.)
    • Carry through any other preserved extension keys verbatim (relationships, lifecycle_changed, tier, base_confidence, …), and the OKF-only keys generated, verified, stale_after, and usage_window so a later export doesn't lose them. These make the round-trip lossless. Treat a bare verified mapping as a one-element list (OKF §5.2).
    • Except what our own exporter derived. Drop generated when generated.by starts with obsidian-wiki/ (it was computed from updated), and drop verified entries whose by is human:vault-owner (computed from the source vault's trust ledger, which doesn't travel). Keeping them would add keys the source page never had. Generated or verified blocks from any other producer are kept.
  4. Reverse-transform body links — markdown links that point at .md paths become wikilinks (this restores both real cross-links and forward-references the exporter preserved per wiki-export Step 3.5):
    • [text](../concepts/transformers.md) or [text](/concepts/transformers.md) → resolve the path (relative to this file's dir, or bundle-root for /-absolute) to a concept id → [[concepts/transformers]], or [[concepts/transformers|text]] when text differs from the target's title. The target's title comes from the bundle page when it exists; otherwise the exporter wrote the target's id as the link text, so treat text equal to the full id (or to its last path segment) as no alias.
    • Treat the markdown target as a file path first: normalize the .md path relative to the current file, then strip the trailing .md from the resolved file path to recover the page id. Do not try to infer the id from directory traversal segments before resolving the full file path. This preserves round-trips for folder-note layouts like projects/social-twitter.md plus projects/social-twitter/..., where ../../social-twitter.md must restore to projects/social-twitter.
    • This applies even when the target page is not in the bundle — a path-form link to a not-yet-written page round-trips back to a dangling [[wikilink]] (Obsidian supports these; OKF §11 forbids rejecting them). Do not leave it as a markdown link.
    • When OBSIDIAN_LINK_FORMAT=markdown is set in config, keep markdown links (just rewrite the path to be vault-relative); do not convert to wikilinks.
    • Leave external http(s):// links and # Citations sections untouched.
  5. Write the page using the conflict mode from Step 2:
    • merge + exists → reverse-map frontmatter and merge it into the existing page (union tags; fill summary/sources only if missing; union relationships; refresh updated). For the body, OKF carries a real body: replace the existing body with the bundle body only if the existing page is a stub (body is just a heading + ## Related); otherwise keep the existing body and append any bundle # Citations / new ## sections not already present. Increm

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars3.5k
CategoryContent
Updated1mo ago
Forks345

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions