CtrlK
BlogDocsLog inGet started
Tessl Logo

wiki-lint

Run a deterministic, read-only health check on an Obsidian wiki. Use for lint, vault health check, audit wiki health, find orphans, find dead links, frontmatter audit, provenance audit, or wiki audit. Reports graph, link, frontmatter, provenance-ledger, empty-section, and stale-index findings; it does not reason broadly or repair files.

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

Passed

No findings from the security scan

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.

The body is a well-structured, actionable instruction skill with strong validation feedback loops and lean prose. The main gaps are minor: a few wordy passages and placeholder path variables that the agent must resolve.

Suggestions

Tighten the deterministic-parser feature paragraph (lines 32-39) into a terse bullet list of reported categories to save tokens.

Add a one-line hint showing how to resolve PRODUCT_ROOT from the skill's own location (e.g. a concrete snippet) so the run command is closer to copy-paste ready.

Consider moving the long list of reported finding categories into a short reference table or keep it inline but as a compact bulleted list for faster scanning.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explanation of what Obsidian or wikilinks are), but a few prose passages such as the deterministic-parser feature list could be trimmed slightly.

4 / 5

Actionability

Provides concrete, mostly copy-paste-ready bash commands with real flags (--vault, --format markdown, --strict), though PRODUCT_ROOT and $VAULT are placeholders the agent must resolve from the skill's own location.

4 / 5

Workflow Clarity

Multi-step Explain-findings and Repair flows are clearly sequenced with explicit validation checkpoints (record expected SHA-256, re-run lint read-only and compare), satisfying the feedback-loop requirement for a read-only/repair operation.

5 / 5

Progressive Disclosure

Well-organized into clear sections with a single clearly-signaled one-level reference; the skill keeps its own content inline rather than splitting into bundle files, leaving minor organization room.

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: concrete actions, comprehensive natural trigger terms, explicit what-and-when guidance, and a clear niche with boundary statements that reduce conflict risk. No improvements needed.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (deterministic read-only health check) and enumerates finding categories (graph, link, frontmatter, provenance-ledger, empty-section, stale-index), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly states what it does ('run a deterministic, read-only health check... reports... findings') and when to use it ('Use for lint, vault health check...'), answering both clearly with concrete triggers.

5 / 5

Trigger Term Quality

The 'Use for lint, vault health check, audit wiki health, find orphans, find dead links, frontmatter audit, provenance audit, or wiki audit' clause provides comprehensive natural synonyms users would actually say.

5 / 5

Distinctiveness Conflict Risk

Scoped tightly to Obsidian wiki linting with a clear niche, and the explicit boundary ('it does not reason broadly or repair files') minimizes overlap with repair or reasoning skills.

5 / 5

Total

20

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
AgriciDaniel/claude-obsidian
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.