docs-cleaner
Consolidates redundant documentation while preserving all valuable content. This skill should be used when users want to clean up documentation bloat, merge redundant docs, reduce documentation sprawl, or consolidate multiple files covering the same topic. Triggers include "clean up docs", "consolidate documentation", "too many doc files", "merge these docs", or when documentation exceeds 500 lines across multiple files covering similar topics.
91
87%
Does it follow best practices?
Impact
96%
1.17xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description with excellent trigger term coverage and completeness. It clearly communicates both purpose and activation conditions with natural language triggers. The main weakness is that the capability description could be more specific about the concrete actions performed during consolidation.
Suggestions
Add 2-3 more specific concrete actions to improve specificity, such as 'identifies duplicate content across files', 'merges overlapping sections', or 'creates unified table of contents'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (documentation) and the core action (consolidates redundant documentation, preserving content), but lacks specific concrete actions like 'identifies duplicates', 'merges sections', or 'removes outdated content'. | 2 / 3 |
Completeness | Clearly answers both what ('Consolidates redundant documentation while preserving all valuable content') and when ('should be used when users want to clean up documentation bloat...') with explicit trigger phrases and even a quantitative threshold (500 lines). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'clean up docs', 'consolidate documentation', 'too many doc files', 'merge these docs', 'documentation bloat', 'documentation sprawl'. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on documentation consolidation/cleanup with distinct triggers. Unlikely to conflict with general documentation writing skills or code-related skills due to specific focus on redundancy reduction and merging. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent workflow clarity and appropriate progressive disclosure. The content is concise and respects Claude's intelligence. The main weakness is the lack of concrete, executable examples - the guidance is procedural but abstract, describing what to do rather than showing specific commands or code snippets for file operations.
Suggestions
Add concrete examples of commands for file operations (e.g., how to count lines across files, how to check for broken links)
Include a brief executable example showing the consolidation of two sample document snippets into one
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, with no unnecessary explanations of concepts Claude already knows. Every section serves a clear purpose with minimal padding. | 3 / 3 |
Actionability | Provides good structural guidance with tables and checklists, but lacks concrete executable examples. The workflow describes what to do conceptually but doesn't include specific commands or code for file operations, link checking, or consolidation. | 2 / 3 |
Workflow Clarity | Clear four-phase workflow with explicit sequencing. Includes a verification checklist before finalizing and addresses error prevention through the anti-patterns table. The phases build logically from discovery to execution. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections and a single reference to external detailed criteria (value_analysis_template.md). Content is appropriately structured for a skill of this scope without being monolithic. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- fernandezbaptiste/claude-code-skills
- Commit
4f0eae8
- 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.