wiki

Initialize, adopt, and route work for a separate Obsidian knowledge vault through the portable claude-obsidian core. Use for vault setup, scaffolding, workspace selection, cross-project configuration, or choosing the correct wiki sub-skill. Triggers: /wiki, set up wiki, scaffold vault, create knowledge base, adopt this vault, Obsidian vault, second brain setup, persistent wiki.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%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 tightly written orchestration skill with executable commands, real validation checkpoints and recovery loops for destructive vault operations, and exemplary progressive disclosure through conditional one-level-deep references. Only minor conciseness trim opportunities exist.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — imperative voice, concrete commands, no concept re-explanation — but the slightly philosophical 'Think, verify, grow' closing and a few guardrail restatements offer minor trim opportunities.	4 / 5
Actionability	Fully executable, copy-paste-ready commands with real flags (--generated-at, --operation-id, --approved-plan-sha256, --apply), a routing table, and concrete checkpoint usage covering the common init/adopt/checkpoint cases.	5 / 5
Workflow Clarity	Destructive/batch operations are sequenced with explicit validation (dry-run by default, preview, then --apply with sha256) and feedback loops ('On a conflict, re-read and rebuild'; 'On interruption, use transaction recover').	5 / 5
Progressive Disclosure	A clear orchestration overview links to well-signaled one-level-deep references (modes, operation-transactions, provenance, install-modes) plus a 'Conditional references' section giving an explicit read-condition per file; all referenced files exist.	5 / 5
	Total	19 / 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 explicitly pairs concrete capabilities with an explicit 'Use for' clause and a rich 'Triggers' list. It is comprehensive on trigger synonyms and distinctiveness, with only minor abstraction in a couple of capability verbs.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Initialize, adopt, and route work', 'vault setup, scaffolding, workspace selection, cross-project configuration'), but a few like 'route work' remain slightly abstract, leaving minor coverage gaps rather than full comprehensiveness.	4 / 5
Completeness	It explicitly answers both 'what' (initialize, adopt, and route work for a separate Obsidian vault) and 'when' via an explicit 'Use for...' clause plus concrete 'Triggers:' phrases, matching the top anchor.	5 / 5
Trigger Term Quality	The 'Triggers:' clause supplies comprehensive natural phrases users would actually say — 'set up wiki', 'scaffold vault', 'create knowledge base', 'adopt this vault', 'Obsidian vault', 'second brain setup', 'persistent wiki' — with strong synonym coverage.	5 / 5
Distinctiveness Conflict Risk	The 'separate Obsidian knowledge vault' / 'portable claude-obsidian core' niche with '/wiki' and 'second brain' triggers is clearly distinct with minimal overlap risk against other skills.	5 / 5
	Total	19 / 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: AgriciDaniel/claude-obsidian
Path: skills/wiki/SKILL.md
Commit: ad67087

Reviewed: 10 days 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.