docs-audit-and-refresh

Audit the repository's docs/ content against the current codebase, find missing, incorrect, or stale documentation, and refresh the affected pages. Use when the user asks to review docs coverage, find outdated docs, compare docs with the current repo, or fix documentation drift across features, settings, tools, or integrations.

Quality

84%

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

85%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, efficient instruction skill with a clear multi-step workflow, explicit validation checkpoint, and appropriate progressive disclosure via a single real reference file. Minor tightening and a few concrete commands would lift conciseness and actionability to top marks.

Dimension	Reasoning	Score
Conciseness	Lean, task-focused body that assumes Claude's competence with no padding about basic concepts; a few sentences (e.g., the qc-helper paragraph) could be tightened, keeping it just below the fully efficient 5 anchor.	4 / 5
Actionability	Concrete, specific guidance with real file paths and an explicit search directive ('search for docs/users/ across .qwen/skills/ and packages/core/src/skills/bundled/'), but as a process skill it stops short of copy-paste commands, leaving minor gaps versus the fully executable 5 anchor.	4 / 5
Workflow Clarity	A clearly sequenced 5-step workflow ending in an explicit 'Validate the refresh' checkpoint with a sub-checklist and feedback-style verification (re-read against code/tests, verify bundled indices), matching the top anchor for batch doc-editing operations.	5 / 5
Progressive Disclosure	Well-organized overview sections with a single, clearly signaled, one-level-deep reference (references/audit-checklist.md, a real file) that holds the bulk high-signal surface list, keeping SKILL.md as a navigable overview per the top anchor.	5 / 5
	Total	18 / 20 Passed

Description

83%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, well-structured description that clearly states capabilities and explicit use-when triggers with natural phrasing. It is concise, third-person, and minimizes conflict risk, with only minor room to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the docs-audit domain and lists several concrete actions (audit docs/, find missing/incorrect/stale docs, refresh pages) with multiple issue classes, matching the 'several specific actions; minor gaps' anchor rather than the more comprehensive 5.	4 / 5
Completeness	Explicitly answers both 'what' (audit, find missing/incorrect/stale, refresh) and 'when' (explicit 'Use when...' clause with concrete trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural user-facing phrases ('review docs coverage', 'find outdated docs', 'compare docs with the current repo', 'fix documentation drift') with good coverage, but lacks synonyms or file extensions that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	The docs-drift/outdated-docs niche is mostly distinct with specific triggers, but 'review docs'/'update docs' phrasing carries minor overlap risk with generic documentation skills.	4 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: QwenLM/qwen-code
Path: .qwen/skills/docs-audit-and-refresh/SKILL.md
Commit: 054eabb

Reviewed: 1 day 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.