CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cs-wiki-linter

Dispatched sub-agent that runs a periodic health check on an LLM Wiki vault. Runs mechanical checks via scripts (orphans, broken links, stale pages, missing frontmatter, duplicate titles, log gaps), does semantic checks (contradictions, stale claims, cross-reference gaps, concepts missing their own page), and produces a markdown report with suggested actions. Spawn weekly, after batch ingests, or when the user says "check the wiki" / "lint my wiki" / "audit the vault".

73

Quality

92%

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

82%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 lean, well-structured dispatched-skill body with concrete commands, explicit thresholds, prioritization rules, and stop conditions. The main weaknesses are minor: the unresolved <plugin> placeholder, no error-handling checkpoint for failed or empty script runs, and reliance on an external workflow file that is not part of the bundle.

Suggestions

Resolve or define the <plugin> placeholder (e.g., state that <plugin> is the dispatching plugin's root path) so the three script commands are copy-paste ready.

Add a validation checkpoint in Pass 1 for script failure or empty JSON output (e.g., re-run with --verbose or report the failure and stop) to close the workflow's only feedback-loop gap.

DimensionReasoningScore

Conciseness

The body is lean and instructional throughout — "The scripts can't catch these. You must read.", "Report, don't silently fix." — with no concept explanations, no padding, and every section (Role, three passes, Rules, Red flags) earning its tokens. Matches the 5 anchor (lean, assumes Claude's competence); it is not 4 because there is nothing that needs trimming.

5 / 5

Actionability

Gives fully flagged commands ("python <plugin>/scripts/lint_wiki.py --vault . --json > /tmp/lint.json", append_log.py with args) and a copy-paste report template, but the "<plugin>" placeholder is never resolved and "concept-shaped nouns" leaves the key semantic instruction unspecified. Matches the 4 anchor (mostly executable with minor gaps); not 5 because the commands are not copy-paste ready as written.

4 / 5

Workflow Clarity

The mechanical → semantic → report → log sequence is clear with explicit thresholds ("older than 90 days", "14+ days", "3+ pages") and stop conditions ("Auto-fixing structural issues without asking → stop"). Matches the 4 anchor (clear sequence, most checkpoints); not 5 because there is no validate/recover step for script failure or empty JSON output, and not 3 because the skill is report-only by design so the destructive-batch cap does not apply.

4 / 5

Progressive Disclosure

Sections are well organized and the single external reference is one level deep and clearly signaled ("Follow `engineering/llm-wiki/skills/llm-wiki/references/lint-workflow.md`. Three passes."), with the body appropriately summarizing rather than duplicating it. Matches the 4 anchor; not 5 because no bundle files accompany the skill, so the referenced workflow doc and scripts under "<plugin>/scripts/" cannot be verified or navigated from the skill alone.

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.

A strong description: it states concrete capabilities for both mechanical and semantic passes, gives explicit scheduling and user-phrase triggers, and occupies a distinct niche. Third-person voice is used and there is no padding.

DimensionReasoningScore

Specificity

Enumerates concrete actions in both mechanical ("orphans, broken links, stale pages, missing frontmatter, duplicate titles, log gaps") and semantic ("contradictions, stale claims, cross-reference gaps, concepts missing their own page") passes plus "produces a markdown report with suggested actions". Comprehensive coverage of its own scope matches the 5 anchor; it is not 4 because no action area is left out.

5 / 5

Completeness

Explicitly answers what ("Runs mechanical checks via scripts... does semantic checks... produces a markdown report with suggested actions") and when ("Spawn weekly, after batch ingests, or when the user says...") with concrete quoted triggers. Matches the 5 anchor exactly; not 4 because the when-clause is fully explicit rather than merely present.

5 / 5

Trigger Term Quality

Includes three natural user phrasings — "check the wiki" / "lint my wiki" / "audit the vault" — plus "health check" and the wiki/vault synonym pair. Matches the 5 anchor's comprehensive natural-term coverage with synonyms; not 4 because no common way a user would phrase this request is missing.

5 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche ("an LLM Wiki vault") with distinct triggers ("lint my wiki" / "audit the vault") that would not plausibly match an unrelated skill. Matches the 5 anchor; not 4 because overlap risk with other skills is minimal, and it uses third-person voice so no voice penalty applies.

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/cs-wiki-linter/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.