wiki-mode

Read or configure the vault filing methodology and suggest destinations for planned knowledge creation under Generic, LYT, PARA, or Zettelkasten. Use for wiki mode, methodology mode, what is my vault mode, set vault mode, switch to PARA, use LYT, Zettelkasten setup, change mode, configure mode, or methodology routing. This skill does not save content or migrate notes.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/wiki-mode/SKILL.md

Quality

Content

75%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 well-structured, actionable body that gives executable commands and a validated transaction workflow without padding. Strengthening the explicit error-recovery loop and concretizing the templates reference would lift it further.

Suggestions

Add an explicit 'if the preview hash mismatch or validation fails, re-run the preview and do not apply' feedback loop to reach the top workflow_clarity anchor.

Replace the vague 'Use the templates under templates/' with a specific file reference (e.g., [templates/para.md](templates/para.md)) so navigation is concrete.

Show one short example of resolving PRODUCT_ROOT and the common $VAULT value to remove the remaining actionability gap.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it does not explain what a vault, PARA, or Zettelkasten is — with only minor trims possible (the closing 'Checkpoint' section is slightly philosophical).	4 / 5
Actionability	Provides concrete, copy-paste-ready commands for get/config/route and a fully specified mode-set transaction with --generated-at, --operation-id, and --approved-plan-sha256 flags; minor gaps remain in resolving placeholders like PRODUCT_ROOT and $VAULT.	4 / 5
Workflow Clarity	The mode-change workflow is a clear 6-step sequence with explicit validation checkpoints (dry-run preview, hash pinning, review-before-apply) and a fail-closed repair note, though the error-recovery feedback loop is less spelled out than the top anchor.	4 / 5
Progressive Disclosure	Well-organized into focused sections (Read and route safely, Change mode, Checkpoint) with a one-level-deep cross-reference to operation-transactions.md; the 'templates/' reference is signalled but not linked to a concrete file, keeping it just short of the top band.	4 / 5
	Total	16 / 20 Passed

Description

83%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 that clearly states both capability and trigger conditions with natural phrasing and a well-scoped niche. Minor tightening of action coverage and a few more synonyms would push it to the top band.

Suggestions

Consider adding the file extension or product name (e.g., 'Obsidian vault') to the trigger terms to further reduce conflict risk with unrelated 'mode' skills.

Add one or two more concrete action verbs (e.g., 'inspect', 'preview') to lift specificity into the comprehensive band.

Dimension	Reasoning	Score
Specificity	Names the domain (vault filing methodology) and several concrete actions — 'Read or configure', 'suggest destinations' — across four named methodologies (Generic, LYT, PARA, Zettelkasten), with only minor coverage gaps relative to a fully comprehensive action list.	4 / 5
Completeness	Explicitly answers what ('Read or configure the vault filing methodology and suggest destinations...') and when ('Use for wiki mode, methodology mode...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes many natural phrases a user would actually say — 'what is my vault mode', 'set vault mode', 'switch to PARA', 'use LYT', 'change mode', 'configure mode' — giving strong keyword coverage, though a few common synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Obsidian vault methodology routing) with distinct, methodology-specific triggers and minimal overlap risk with unrelated skills; not quite maximal because 'change mode'/'configure mode' are somewhat generic.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: AgriciDaniel/claude-obsidian
Path: skills/wiki-mode/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.