CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wiki-lint

Run a health check on the LLM Wiki vault — mechanical checks (orphans, broken links, stale pages, missing frontmatter, log gap, duplicates) plus semantic checks (contradictions, cross-reference gaps, concepts missing their own page). Outputs a markdown report with suggested actions. Usage /wiki-lint [--stale-days N] [--log-gap-days N]

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/wiki-lint/SKILL.md
SKILL.md
Quality
Evals
Security

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, lean command document with a clearly sequenced three-pass workflow, concrete CLI and script references, and an explicit report format. The recurring weaknesses are mild: some duplicated content, implicit validation checkpoints, and references that resolve only against the wider repo rather than the skill bundle itself.

Suggestions

Deduplicate the script listings — drop the standalone "Scripts" section (or the inline Pass 1 paths) and fold the intro's cadence sentence into the Frequency table.

Add a brief explicit checkpoint between passes, e.g. "If Pass 1 errors, stop and report the script failure" — and clarify where the wiki-linter sub-agent dispatch sits relative to Passes 1–3.

Use bundle-relative paths for the scripts and references (scripts/lint_wiki.py rather than the repo-root-relative engineering/llm-wiki/... prefix) so the skill is navigable as a standalone bundle.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no concept over-explanation, and the report template and frequency table earn their tokens. Minor waste: the two script paths are listed in both "Pass 1" and "Scripts", and the intro line "Run this weekly, after batch ingests, and always before sharing the wiki" duplicates the Frequency table, fitting the 4 anchor (trimmable instances) rather than 5.

4 / 5

Actionability

Concrete, executable guidance dominates: exact CLI invocations with flag examples ("/wiki-lint --stale-days 60"), exact script paths, a concrete report format, and an explicit safety stance ("Reports, doesn't silently fix"). Minor gaps keep it at 4 rather than 5: the semantic-pass methodology is delegated wholesale to agents/wiki-linter.md, and the report template retains "..." placeholders.

4 / 5

Workflow Clarity

The three passes are explicitly sequenced (mechanical scripts → semantic reads → report), with a defined log append as the closing step, and the operation is read-only so the destructive/batch validation cap does not apply. It sits at 4 rather than 5 because checkpoints are implicit (no step to verify script output before the semantic pass) and how the sub-agent dispatch interleaves with the passes is unstated.

4 / 5

Progressive Disclosure

Sections are well organized and external references are clearly signaled and one level deep (arrows to lint-workflow.md, SKILL.md, and the sub-agent doc). Scored against the actual bundle structure, however, no references/, scripts/, or agents/ files exist in the bundle — every referenced path is an external repo-root-relative path — so navigation depends entirely on the surrounding repo layout; this minor organization gap fits the 4 anchor rather than 5.

4 / 5

Total

16

/

20

Passed

Description

75%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 highly specific, well-scoped description with a clear niche and strong trigger vocabulary, written in third person with concrete capability enumeration. Its one material weakness is the absence of any "Use when..." (or equivalent) trigger guidance, which caps completeness and limits how reliably a user or Claude will invoke it at the right moments.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to check, audit, or lint the wiki, or before sharing the wiki or after a batch ingest."

Broaden natural trigger synonyms to include "audit", "wiki maintenance", and "dead links" alongside the existing "health check"/"broken links" terms.

State cadence triggers in the description (weekly, after batch ingests, before sharing) since the body already defines them — this doubles as implicit "when" guidance.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — "orphans, broken links, stale pages, missing frontmatter, log gap, duplicates" plus semantic checks "contradictions, cross-reference gaps, concepts missing their own page" — and names the concrete output artifact ("Outputs a markdown report with suggested actions"). This matches the 5 anchor (comprehensive coverage of specific concrete actions); it is not 4 because no capability area is left unnamed or generic.

5 / 5

Completeness

The "what" is clearly and concretely answered, but there is no "Use when..." clause or equivalent trigger guidance — the "Usage /wiki-lint [--stale-days N]" line documents invocation syntax, not when to reach for the skill. Per the rubric guideline, a missing explicit trigger clause caps completeness at 3 even with a strong "what".

3 / 5

Trigger Term Quality

Good natural keyword coverage: "health check", "wiki", "orphans", "broken links", "stale", "contradictions", "lint" are phrases a user would plausibly say. A few natural synonyms are missing ("audit the wiki", "wiki maintenance", "dead links"), so it fits the 4 anchor rather than the 5 anchor's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche — linting a specific "LLM Wiki vault" — with distinct trigger vocabulary (orphans, wikilinks, log gap) that no general-purpose skill would claim. Minimal overlap risk; matches the 5 anchor.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

alirezarezvani/claude-skills

Path

.gemini/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.