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.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%

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-sequenced, actionable editorial workflow with validation checkpoints and a completion checklist. Its main weaknesses are structural repetition across the Baseline/Procedure/Pass-Criteria sections and a heading-hierarchy defect that leaves the procedure steps visually orphaned under the Validation Tool heading.

Suggestions

Remove the duplication between 'Baseline actions', Procedure steps 4-8, and 'Pass Criteria' — the same categories (syntax, link integrity, heading hierarchy, code-block tags) appear three times; consolidate so each category is stated once and referenced from the checklist.

Fix the heading hierarchy: make '## Procedure' the parent of the numbered '### 1'…'### 10' subsections (e.g., move the 'Validation Tool' block inside Procedure or beneath it) so the steps are not mis-nested under an unrelated H2.

Consider merging 'Style Rules' and 'Safety Rules' into the Procedure or a single constraints section, since several rules (preserve meaning, no inventing claims, concise tone) restate guidance already enforced in the steps and Pass Criteria.

Dimension	Reasoning	Score
Conciseness	Per-section bullets are tight and avoid explaining concepts Claude already knows, but the same categories (syntax, link integrity, heading hierarchy, code-block tags) are restated across Baseline actions, Procedure steps 4-8, and Pass Criteria, adding redundant tokens.	2 / 3
Actionability	Provides copy-paste-ready commands (test/check-docs, --fix flag, per-file invocation) and concrete actionable bullets such as 'avoid skipped levels (## directly to ####)' and language-tag examples; for an instruction-only editorial skill the guidance is specific and actionable.	3 / 3
Workflow Clarity	A clear 10-step numbered sequence with explicit validation checkpoints (run test/check-docs to establish a baseline in step 3, completion checklist in step 9), a confirm-target/confirm-depth preamble, and branching guidance for minimal vs. broad cleanup.	3 / 3
Progressive Disclosure	Single-file layout is appropriate for a procedural skill with no external references, but a heading-hierarchy defect — an empty '## Procedure' followed by '## Validation Tool' leaves the '### 1' through '### 10' steps mis-nested under Validation Tool — hurts navigation.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 well-crafted description: it states concrete capabilities, includes an explicit 'Use when' trigger with natural phrasing, and is scoped tightly to wiki markdown cleanup. It is concise without padding and clearly distinguishable from adjacent skills.

Dimension	Reasoning	Score
Specificity	Lists five distinct concrete actions (syntax correctness, readability, link integrity, heading hierarchy normalization, code block language tagging), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly answers both 'what' (five concrete doc-fixing actions) and 'when' via an explicit 'Use when a user asks to clean up markdown formatting...' trigger clause.	3 / 3
Trigger Term Quality	Phrases like 'clean up markdown formatting' and 'improve clarity while preserving technical meaning' are natural terms a user would say when requesting this skill, giving good trigger coverage.	3 / 3
Distinctiveness Conflict Risk	The 'wiki markdown docs' scope and cleanup-formatting triggers carve a clear niche unlikely to fire for non-markdown or non-editorial skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: vladmandic/sdnext
Path: .github/skills/update-docs/SKILL.md
Commit: 058a7f0

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

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.