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-importInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
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.
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.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| wiki-import (this skill)by Ar9av | 95 | 3.5k | 54d ago | SKILL.md |
| siyuanby siyuan-note | 100 | 47.3k | today | MCP Server |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.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.
Skill content
View source on GitHubname: 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## Relatedlink 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.
- 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. - Read
$OBSIDIAN_VAULT_PATH/AGENTS.mdif 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
.mdfiles with OKF frontmatter (atype:key), and/or a rootindex.mdwithokf_version→ OKF bundle import (skip Step 3; go to Step 4-OKF). Bothokf_version0.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
.mdfile (i.e. notindex.md/log.md) with parseable YAML frontmatter containing a non-emptytype. - A
.mdwith no frontmatter or notypeis 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:
- Compute
page_path = $VAULT/<node.id>.md - Ensure the parent directory exists (e.g.
$VAULT/concepts/) - 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
- merge mode (default) + exists → read existing file, apply merge logic (see below), increment
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)
- Read the existing page's frontmatter.
- Tags: union of existing tags and
node.tags(deduplicated, keep existing order, append new ones). - Summary: if the existing page has no
summaryfield andnode.summaryexists, add it. - Relationships: union of existing
relationships:entries andtyped_edges[node.id]— skip entries where the same(target, type)pair already exists. - Updated: set
updatedto the current ISO timestamp. - Body: scan for a
## Relatedsection. If it exists, append any missing wikilinks fromadjacency[node.id]that aren't already linked anywhere in the body. If no## Relatedsection exists, append one with the missing links. - 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):
- Parse the YAML frontmatter. If it has no frontmatter or no non-empty
type, incrementunparseableand skip the file. - Compute the concept id = the file's path relative to the bundle root, with
.mdstripped (e.g.concepts/transformers.md→concepts/transformers). The target page is$VAULT/<concept-id>.md. - Reverse-map frontmatter (the inverse of the canonical mapping table in
wiki-exportStep 3.5):title←title.category← the preservedcategoryextension key if present; else lower-case the directory prefix of the concept id (concepts/…→concepts); else derive fromtype(Concept→concepts,Entity→entities,Skill→skills,Reference→references,Synthesis→synthesis,Project→projects,Journal→journal).tags←tags.summary←description.updated← the preservedupdatedextension key if present; elsegenerated.at; else a legacy v0.1timestamp; else now.created← the preservedcreatedextension key if present, else now.sources← OKFsources, as a list of strings: for each entry that is a mapping, take itsresource; keep plain strings as-is (that's how v0.1 bundles from older exports carried our native list). If the bundle has nosources, use["imported from OKF bundle <bundle path>"]. If a top-levelresourceURL is present and not already in the list, add it.lifecycle← the preservedlifecycleextension key if present; else fromstatus:draft→draft,deprecated→archived,stableor absent → leavelifecycleunset. (OKF has no equivalent ofreviewed/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 keysgenerated,verified,stale_after, andusage_windowso a later export doesn't lose them. These make the round-trip lossless. Treat a bareverifiedmapping as a one-element list (OKF §5.2). - Except what our own exporter derived. Drop
generatedwhengenerated.bystarts withobsidian-wiki/(it was computed fromupdated), and dropverifiedentries whosebyishuman: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.
- Reverse-transform body links — markdown links that point at
.mdpaths become wikilinks (this restores both real cross-links and forward-references the exporter preserved perwiki-exportStep 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]]whentextdiffers 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
.mdpath relative to the current file, then strip the trailing.mdfrom 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 likeprojects/social-twitter.mdplusprojects/social-twitter/..., where../../social-twitter.mdmust restore toprojects/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=markdownis 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# Citationssections untouched.
- Write the page using the conflict mode from Step 2:
- merge + exists → reverse-map frontmatter and merge it into the existing page (union
tags; fillsummary/sourcesonly if missing; unionrelationships; refreshupdated). 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
- merge + exists → reverse-map frontmatter and merge it into the existing page (union
Truncated for display — read the full file on GitHub.
Related Skills
siyuan
47.3kAn open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
