CtrlK
BlogDocsLog inGet started
Tessl Logo

update-docs

Update wiki markdown docs for syntax correctness, readability, link integrity, heading hierarchy normalization, and code block language tagging. Use when a user asks to clean up markdown formatting and improve clarity while preserving technical meaning.

67

Quality

81%

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

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, actionable procedural skill with validation checkpoints and a completion checklist. Main improvements are removing the empty '## Procedure' heading, de-duplicating tone constraints, and adding an explicit validation retry loop.

Suggestions

Remove or fill the empty '## Procedure' heading — step headings currently sit as siblings under 'Validation Tool' rather than nested under 'Procedure'.

De-duplicate tone/style guidance: state it once in 'Style Rules' and reference it from step 6 instead of restating 'concise technical phrasing, approachable wording, no unexplained technical babble'.

Add an explicit retry loop in step 9 (e.g., 'If test/check-docs fails, fix the reported issues and re-run until it passes') to reach the workflow_clarity 5 anchor.

DimensionReasoningScore

Conciseness

Lean and free of concept padding, but tone/style constraints are restated across 'Style Rules', 'Safety Rules', and step 6, and the '## Procedure' heading is empty — minor trim opportunities.

4 / 5

Actionability

Concrete commands ('test/check-docs', 'test/check-docs --fix wiki/File.md') and specific fix categories give mostly executable guidance; editorial steps are directional rather than command-driven, appropriate for this skill.

4 / 5

Workflow Clarity

A clear 10-step sequence with before/after validation via test/check-docs and a completion checklist; however an explicit 'if validation fails, fix and re-run' retry loop is not stated in the procedure.

4 / 5

Progressive Disclosure

Single well-organized SKILL.md with clearly signaled sections and no nested references; no external bundle files are needed, though at ~185 lines the simple-skill 5 exception does not cleanly apply.

4 / 5

Total

16

/

20

Passed

Description

88%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, specific description that clearly states capabilities and an explicit use-trigger, with comprehensive action coverage. The only gap is slightly thinner natural-keyword coverage (no file extensions or synonyms).

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'syntax correctness, readability, link integrity, heading hierarchy normalization, and code block language tagging' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (the five cleanup actions) and 'when' via a concrete 'Use when a user asks to clean up markdown formatting...' trigger clause.

5 / 5

Trigger Term Quality

Natural phrases like 'clean up markdown formatting' and 'improve clarity' are present, but file extensions (.md) and common synonyms (polish, normalize, lint) are missing.

4 / 5

Distinctiveness Conflict Risk

The wiki-markdown cleanup niche with heading/code-block normalization is mostly distinct, with only minor overlap risk against general markdown-lint 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.

Validation15 / 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
vladmandic/sdnext
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.