wiki-setup

Initialize a new Obsidian wiki vault with the correct structure, special files, and configuration. Use this skill when the user wants to set up a new wiki from scratch, initialize the vault structure, create the .env file, or says things like "set up my wiki", "initialize obsidian", "create a new vault", "get started with the wiki". Also use when the user needs to reconfigure their existing vault or fix a broken setup.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

63%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, actionable setup workflow with clear sequencing and a verification checklist, but it is verbose and monolithic: substantial optional sections (QMD exclusions, Stop hook, GitHub sync) are inlined in SKILL.md rather than split into reference files. Actionability is strong, held back only by template placeholders.

Suggestions

Move the Stop-hook installation and GitHub-sync sections into separate reference files (e.g. references/stop-hook.md, references/github-sync.md) and keep SKILL.md as an overview with one-level-deep links, improving both conciseness and progressive disclosure.

Tighten the QMD `_raw/` exclusion prose in Step 1.4 into a short imperative checklist (read index.yml → check ignore block → add `_raw/**` → run `qmd update`), relocating the rationale to a reference if needed.

Replace `<HOOK_PATH>`/`<collection-name>` style placeholders with concrete resolved examples or a single explicit resolution step so commands are copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Mostly actionable but noticeably long; the QMD `_raw/` exclusion prose (Step 1.4) and the Stop-hook installation block (including the duplicate-nudge note) are detailed enough that they could be trimmed or moved to references.	3 / 5
Actionability	Provides copy-paste-ready commands and full file templates (mkdir brace expansion, .obsidian JSON, index/log/hot markdown), but placeholders like `<HOOK_PATH>`, `<collection-name>`, and `TIMESTAMP` require substitution, keeping it just short of fully executable.	4 / 5
Workflow Clarity	Steps 1-6 are clearly sequenced and Step 6 is an explicit verification checklist; the QMD section adds a verify→fix→re-run feedback loop. Minor gap: no validate-fix-retry on the core file creation itself, only a final checklist.	4 / 5
Progressive Disclosure	Well-sectioned with Steps and Optional headers, but no bundle/reference files exist and all content — QMD config detail, Stop-hook install, GitHub sync — is inlined in one ~300-line file rather than split into one-level-deep references.	3 / 5
	Total	14 / 20 Passed

Description

100%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.

An exemplary description: it states concrete capabilities, gives explicit 'Use when...' guidance with varied natural trigger phrases, and occupies a distinct niche unlikely to fire for sibling wiki skills. Both the what and when are answered clearly and specifically.

Dimension	Reasoning	Score
Specificity	Names the domain (Obsidian wiki vault) and multiple concrete actions — 'initialize the vault structure', 'create the .env file', 'create special files', 'reconfigure their existing vault', 'fix a broken setup' — giving comprehensive coverage rather than just 1-2 actions.	5 / 5
Completeness	Explicitly answers both what ('Initialize a new Obsidian wiki vault with the correct structure, special files, and configuration') and when ('Use this skill when... or says things like...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users actually say with synonym variation — 'set up my wiki', 'initialize obsidian', 'create a new vault', 'get started with the wiki' — covering the natural ways a user would request setup.	5 / 5
Distinctiveness Conflict Risk	Targets a clear niche (vault initialization/repair) with distinct setup-focused triggers; sibling wiki-* skills handle ingest/query/capture, so conflict risk is minimal.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Ar9av/obsidian-wiki
Path: .skills/wiki-setup/SKILL.md
Commit: 52c9f2b

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.