CtrlK
BlogDocsLog inGet started
Tessl Logo

wiki-import

Import a wiki knowledge graph into the current vault — either from a graph.json export file (stubs) or from an OKF (Open Knowledge Format) markdown bundle (full page bodies). Use this skill when the user says "import wiki", "import from export", "load graph.json", "import vault", "import OKF bundle", "import OKF", "load OKF", "import markdown bundle", "/wiki-import", or wants to transfer pages from one vault to another using the output of wiki-export.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, well-structured dual-source import workflow with concrete templates and formats, weakened mainly by the absence of a post-write verification step on a batch operation and some repeated conflict-mode prose. Conciseness and progressive disclosure are good but not maximal given the file's length and inline detail.

Suggestions

Add a post-write verification checkpoint in Step 5 or 6 (e.g., re-parse a sample of written pages and confirm wikilink targets exist) so the batch workflow clears the workflow_clarity cap above 3.

Factor the repeated merge/skip/overwrite mode table (Step 2) into a single authoritative reference and point Step 4-Graph and Step 4-OKF at it instead of re-enumerating the six branches in each.

Move the detailed OKF reverse-mapping table and page template into a references/ file (e.g. OKF_MAPPING.md) referenced one level deep, to reduce the inline SKILL.md length and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body assumes Claude knows what vaults, wikilinks, and frontmatter are and stays dense for a dual-source workflow, but the merge/skip/overwrite mode enumeration is repeated across Step 2, Step 4-Graph, and Step 4-OKF and could be tightened.

4 / 5

Actionability

Provides concrete page templates, a reverse-mapping table, explicit path-resolution rules, and exact manifest/index/log/hot entry formats that are mostly copy-paste ready, with only minor gaps (e.g., YAML parsing mechanics left implicit).

4 / 5

Workflow Clarity

Steps 1–6 are clearly sequenced with input validation and a preview in Step 1, but this is a batch/destructive operation with no post-write verification checkpoint that written pages parse or wikilinks resolve, so the rubric's batch-operation cap at 3 applies.

3 / 5

Progressive Disclosure

No bundle files exist and the single SKILL.md is well sectioned into Steps 1–6 plus Notes, but at ~273 lines the detailed reverse-mapping spec and templates are inlined where a one-level-deep reference file could improve navigability.

4 / 5

Total

15

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that concretely names both source types and their outcomes and pairs an explicit 'what' with an exhaustive trigger-phrase 'when' clause. The only mild gap is action-verb breadth, which keeps specificity at 4 rather than 5.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — reconstructing stubs from graph.json and full pages from an OKF bundle — but the action verbs stay close to 'import/reconstruct' rather than enumerating a broad set, leaving minor coverage gaps versus the comprehensive 5-anchor.

4 / 5

Completeness

Explicitly states what the skill does (import a wiki knowledge graph from graph.json stubs or an OKF bundle) and when to use it via a concrete 'Use this skill when the user says…' clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

Lists a comprehensive set of natural trigger phrases a user would actually say ('import wiki', 'load graph.json', 'import OKF bundle', 'import markdown bundle', '/wiki-import') including synonyms and the slash-command form.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — vault-to-vault wiki import paired with wiki-export — with distinct, import-specific triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository
Ar9av/obsidian-wiki
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.