CtrlK
BlogDocsLog inGet started
Tessl Logo

wiki-lint

Audit and maintain the health of the Obsidian wiki. Use this skill when the user wants to check their wiki for issues, find orphaned pages, detect contradictions, identify stale content, fix broken wikilinks, or perform general maintenance on their knowledge base. Also triggers on "clean up the wiki", "what needs fixing", "audit my notes", or "wiki health check". Add --consolidate to switch from report-only to act-and-report mode (the "dream cycle"): fixes broken links, adds missing cross-references for orphans, corrects lifecycle states, demotes stale peripheral pages, normalizes tag aliases, and adds contradiction callouts — all with a dry-run preview and explicit user confirmation before any writes.

72

Quality

90%

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

81%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, highly actionable lint skill with strong sequencing and validation for its destructive consolidate mode. The main weaknesses are length (inline report/output templates that could be factored out) and a handful of checks described procedurally rather than as executable commands.

Suggestions

Move the full consolidation-report markdown template and the dry-run output example into a reference file (e.g. references/consolidate-template.md) and link to it, reducing SKILL.md length and improving progressive_disclosure.

Convert the remaining procedural checks (orphaned pages, broken wikilinks, contradictions) into concrete grep/glob command snippets like the synthesis-gaps section already provides, to lift actionability from 4 to 5.

Tighten the duplicated log-entry format strings (the LINT and LINT_CONSOLIDATE lines) into a single referenceable template to trim redundant tokens.

DimensionReasoningScore

Conciseness

The body is dense and almost entirely actionable with no basic-concept padding, but at ~600 lines it includes long inline templates (consolidation report, dry-run output, full output-format block) that could be trimmed or factored out.

4 / 5

Actionability

Most checks give executable specifics (exact grep patterns, thresholds like 'AMBIGUOUS > 15%', 'cohesion < 0.15', real bash for trust-check/trust-record), but a few checks are described as procedural steps rather than copy-paste commands (e.g., contradictions, orphan detection).

4 / 5

Workflow Clarity

Sequenced 'Before You Start' steps, ordered lint checks, and a consolidate mode with explicit validation checkpoints (dry-run preview, user confirmation, git pre-write snapshot, trust-check --strict) plus error-recovery feedback loops for a batch/destructive operation.

5 / 5

Progressive Disclosure

Well-sectioned single file with clearly signaled one-level-deep references to llm-wiki/SKILL.md for config/provenance/lifecycle detail; no bundle files exist, and large inline output templates are the main organization gap.

4 / 5

Total

17

/

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.

The description is exemplary: it states concrete capabilities, gives explicit 'when to use' guidance with natural trigger phrases, and carves out a distinct niche with a clear consolidate-mode differentiator. It uses third person voice throughout and avoids fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete audit actions ('find orphaned pages, detect contradictions, identify stale content, fix broken wikilinks') plus six consolidate actions, giving comprehensive coverage of capabilities.

5 / 5

Completeness

Explicitly answers both what ('Audit and maintain the health of the Obsidian wiki') and when ('Use this skill when the user wants to check their wiki for issues... Also triggers on...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases verbatim ('clean up the wiki', 'what needs fixing', 'audit my notes', 'wiki health check') alongside technical terms, covering synonyms and phrasings users would actually say.

5 / 5

Distinctiveness Conflict Risk

Clear niche (Obsidian wiki health audit) with distinct triggers and a unique --consolidate mode; minimal overlap risk with other skills.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (629 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

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.