CtrlK
BlogDocsLog inGet started
Tessl Logo

wiki-lint

Use when an LLM Wiki operation issue is a lint or health check. Audit for contradictions, orphans, weak provenance, broken links, missing concept pages, and index/log drift; return triage findings without auto-fixing.

75

Quality

92%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary read-only audit skill: lean, highly actionable, with a well-sequenced workflow and a verification checklist, all in a single self-contained well-organized file.

DimensionReasoningScore

Conciseness

Lean, instruction-only body with no padding about what a wiki is; every section (Inputs, Workflow, Voice, Verification, Tools) earns its place and assumes Claude's competence, matching the 'every token earns its place' anchor; not 2 because there is no unnecessary explanation to tighten.

3 / 3

Actionability

Concrete executable guidance throughout: named tools, a quantified threshold ('a term appears on three or more pages'), exact severity groupings, and a copy-paste log-entry template — fully actionable for an instruction-only skill; not 2 because nothing is pseudocode or missing key details.

3 / 3

Workflow Clarity

A clear numbered 5-step sequence capped by an explicit Verification checklist; the destructive/batch feedback-loop cap does not apply because lint is read-only by design, and the checklist provides the validation checkpoint the anchor 3 expects.

3 / 3

Progressive Disclosure

A short, self-contained skill organized into clearly delineated sections with no nested or multi-level references; per the simple-skills note, a compact well-sectioned skill with no need for external files can score 3 on organization alone; not 2 because nothing that should be separate is left inline and references are not poorly signaled.

3 / 3

Total

12

/

12

Passed

Description

85%

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, specific description with an explicit trigger clause and a clear niche; its only weakness is trigger phrasing tied to internal 'operation issue' jargon rather than natural user language.

Suggestions

Add natural user-side phrasing to the trigger, e.g. 'Use when asked to audit, lint, or run a health check on an LLM Wiki space' so it matches what a user would actually say.

Include common keyword variations (audit, broken links, stale pages) alongside 'lint or health check' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Audit for contradictions, orphans, weak provenance, broken links, missing concept pages, and index/log drift; return triage findings without auto-fixing' — matching the anchor for several specific concrete actions rather than the partial domain-only anchor at 2.

3 / 3

Completeness

Answers both 'what' (audit six issue types, return triage findings, no auto-fix) and 'when' via the explicit 'Use when an LLM Wiki operation issue is a lint or health check' clause, satisfying the anchor that requires an explicit trigger; the guideline's cap at 2 for a missing 'Use when' clause does not apply.

3 / 3

Trigger Term Quality

Includes natural terms 'lint' and 'health check', but the trigger is gated on the system-specific jargon 'an LLM Wiki operation issue' rather than phrasing a user would naturally say, and it omits common variations like 'audit', 'check the wiki', or 'find broken links'. Not 3 because coverage of natural user terms is incomplete; not 1 because lint/health-check are genuine natural keywords.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (wiki-space linting/health checks) with distinct triggers unlikely to fire for unrelated skills; not 2 because it is far more specific than 'Works with document files'.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
paperclipai/paperclip
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.