CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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".

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

68%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-organized, largely actionable lint procedure with specific thresholds, patterns, and a defined output contract. Its main weakness is the absence of validation/verification after fixes — the remediation steps are batch vault-wide edits with no re-lint or verification loop, which caps workflow clarity — plus a somewhat padded example report.

Suggestions

Add a verification loop after fixes: re-run the affected lint check (or the full audit) to confirm each issue is resolved before logging, e.g. 'After fixing, re-run the check and only then append to log.md'.

Trim the ~55-line example report in the Output Format section to one illustrative line per finding type, or move the full template to a reference file.

Give the stale-content and contradiction checks the same concreteness as the others — e.g. a stat/comparison command for source-vs-page timestamps and specific grep patterns for contradiction-signal phrases.

DimensionReasoningScore

Conciseness

Largely lean procedural checklists that assume Claude's competence (no explanations of grep, wikilinks, or frontmatter), but the ~55-line fabricated example report in the Output Format section and some check narratives could be trimmed — minor over-explanation, matching anchor 4 rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Mostly executable guidance: concrete grep patterns ('\[\[.*?\]\]', '^summary:'), numeric thresholds (cohesion < 0.15, AMBIGUOUS > 15%, INFERRED > 40%), a runnable grep/comm snippet, and specific paths (.env, _meta/taxonomy.md, misc/). Minor gaps: the stale-content and contradiction checks give direction but no concrete commands.

4 / 5

Workflow Clarity

The sequence is clear (Before You Start → checks in order → structured report → log entry → offer fixes), but the fixes are batch vault-wide operations (mass wikilink insertion, page moves, backlink rewrites) with no validation or re-lint step to confirm resolution — per the rubric's batch-operations cap, this cannot score above 3.

3 / 5

Progressive Disclosure

No bundle files exist, and the ~245-line body is well-sectioned with clearly signaled one-level-deep cross-references to sibling suite skills (llm-wiki/SKILL.md Retrieval Primitives, cross-linker, /wiki-synthesize). Good structure with minor gaps: the 11 detailed checks could be split into reference files, and the external references depend on skills outside this bundle.

4 / 5

Total

15

/

20

Passed

Description

91%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 explicitly states what the skill does and when to use it, with exemplary quoted trigger phrases. The only weaknesses are modest: it under-advertises roughly half of the skill's actual checks, and one trigger phrase ('what needs fixing') is broad enough to risk cross-firing with unrelated maintenance requests.

DimensionReasoningScore

Specificity

Lists several concrete actions ('find orphaned pages, detect contradictions, identify stale content, fix broken wikilinks'), but the body contains 11 checks and the description omits frontmatter, provenance, tag clusters, visibility, promotion, and synthesis gaps — more than a minor coverage gap, so not a 5.

4 / 5

Completeness

Explicitly answers both questions: 'what' via 'Audit and maintain the health of the Obsidian wiki' with enumerated actions, and 'when' via 'Use this skill when the user wants to...' plus concrete quoted trigger phrases — a direct match to the anchor-5 example.

5 / 5

Trigger Term Quality

Four quoted natural trigger phrases ('clean up the wiki', 'what needs fixing', 'audit my notes', 'wiki health check') plus capability keywords users would echo ('check their wiki for issues', 'knowledge base') give comprehensive natural-term coverage for the Obsidian-notes domain.

5 / 5

Distinctiveness Conflict Risk

'Obsidian wiki' carves a clear niche with domain-anchored triggers, but 'what needs fixing' is generic enough to collide with code-review/maintenance skills, and the skill overlaps its own sibling wiki-suite skills (cross-linker, wiki-synthesize) — minor overlap risk with closely related skills.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

saski/arnesto

Path

.agents/skills/wiki-lint/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.