wiki-import brings knowledge exported from another vault into the current one. It accepts a graph.json file, which rebuilds page stubs with frontmatter, typed relationships and a Related list, or an OKF bundle, which rebuilds full pages with their original bodies.
It shows a preview, resolves conflicts in merge, skip or overwrite mode, writes the pages, and records the import in the manifest, index, log and hot context.
What You Get
- Pages created in the right category folders with valid frontmatter
- Full page bodies from an OKF bundle, or stubs with a Related section from graph.json
- Typed relationships and tags merged into pages that already exist
- An updated manifest, index, log and hot file recording the import
- A summary of created, merged, skipped and unparseable pages
Common Use Cases
- Moving a whole wiki from one vault to another without losing page content
- Seeding a new vault from a shared graph.json skeleton
- Merging a teammate’s exported pages into your own vault
What Makes It Unique
It is the reverse half of wiki-export and understands both of its outputs, using the lossy graph file for structure and the OKF bundle for content. Its conflict modes are chosen from the user’s phrasing, and the OKF path restores dangling links, preserves extension keys and drops fields its own exporter derived. Metadata is written through one locked command so parallel writers cannot drop updates.
Under The Hood
The skill is instructions for the agent. It reads the export source, writes markdown pages and edits the manifest file in the vault. It runs the obsidian-wiki command line tool to sync the index, log and hot files under a lock, and it tells the agent never to edit those three by hand. It does not fetch web pages or call remote APIs.