CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wiki-setup

Initialize or repair an Obsidian wiki vault's required structure and configuration. Use for new-vault setup, .env/config creation, reconfiguration, or broken setup recovery.

Quality

83%

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

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

Highly actionable and well-sequenced setup guidance with executable code, complete file templates, and explicit validation, but it pays for that in length: the monolithic 370-line body inlines detail that belongs in reference files and contains padded passages and a numbering defect in Step 1. Tightening the QMD/hook sections into references and fixing the duplicated question numbering would lift both weak dimensions.

Suggestions

Fix the Step 1 numbering (two questions are both numbered '5') and move the misplaced QMD sub-bullets ('If using CLI mode, set QMD_CLI_SEARCH_MODE...', 'If unsure, skip for now...') out of the timezone question into the QMD question.

Move the stop-hook installation steps and the QMD _raw/ collection-management detail into reference files (e.g., references/stop-hook.md, references/qmd-setup.md) and keep one-line pointers in SKILL.md.

Add a fix-and-re-verify loop to Step 6 (e.g., 'if any check fails, fix the missing file/dir and re-run the checklist') and trim rationale passages such as the duplicate-nudge blockquote to essentials.

DimensionReasoningScore

Conciseness

Mostly dense repo-specific operational detail Claude could not know, but several padded passages could be trimmed: the 13-line QMD _raw/ bullet mixing config, rationale, and remediation; the 'duplicate nudge' blockquote; and QMD-update guidance repeated between Step 1 and the final section.

3 / 5

Actionability

Guidance is copy-paste executable throughout: full bash for config resolution and template discovery, mkdir structure, printf manifest creation, complete index.md/log.md/hot.md templates, Obsidian JSON configs, sync-setup commands, and curl fallback covering packaged, source, and older-wheel layouts.

5 / 5

Workflow Clarity

Steps 1-6 are clearly sequenced with an explicit Step 6 verification checklist and no-clobber safeguards for existing files. Minor gaps remain: two Step 1 questions are both numbered '5', QMD sub-bullets sit misplaced under the timezone question, and Step 6 is a report-only checklist with no fix-and-re-verify loop.

4 / 5

Progressive Disclosure

Section headers are clear and cross-skill references (wiki-ingest/SKILL.md, llm-wiki/SKILL.md, .env.example) are named, but no reference files exist and ~120 lines of stop-hook installation and QMD collection management detail are inlined in this 370-line SKILL.md rather than split out.

3 / 5

Total

15

/

20

Passed

Description

87%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 description: concise, third-person, with a clear what-and-when structure and concrete trigger phrases for setup, reconfiguration, and recovery scenarios. Only minor term-coverage and capability-coverage gaps keep specificity and trigger quality at 4.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Initialize or repair an Obsidian wiki vault's required structure and configuration' plus '.env/config creation' — matching the several-specific-actions anchor with minor gaps (plugin recommendations, GitHub sync, hook setup are unmentioned).

4 / 5

Completeness

It explicitly answers both questions: a clear 'what' ('Initialize or repair an Obsidian wiki vault's required structure and configuration') and a concrete 'when' ('Use for new-vault setup, .env/config creation, reconfiguration, or broken setup recovery'), matching the top anchor.

5 / 5

Trigger Term Quality

Natural terms users would say are well covered ('Obsidian', 'wiki vault', 'new-vault setup', '.env', 'config', 'reconfiguration', 'broken setup recovery'), but a few natural variations (e.g., 'initialize', 'knowledge base') are missing.

4 / 5

Distinctiveness Conflict Risk

'Obsidian wiki vault' setup/repair is a clear niche with distinct triggers that separate it from sibling ingest/query/status skills; overlap risk is minimal.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

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.