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.
Install with Tessl CLI
npx tessl i github:daymade/claude-code-skills --skill docs-cleanerOverall
score
88%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
90%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 when to use the skill with multiple natural language triggers and even includes a quantitative threshold. The main weakness is that the 'what' portion could be more specific about the concrete actions performed during consolidation.
Suggestions
Add 2-3 more specific actions to the capability description, such as 'identifies duplicate content', '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, merge redundant docs...') 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 conciseness. The four-phase approach with validation checklist demonstrates good process design. The main weakness is the lack of concrete, executable examples - the guidance is clear but somewhat abstract, particularly around the actual file manipulation and consolidation steps.
Suggestions
Add a concrete example showing actual file content before/after consolidation (even a small snippet)
Include specific commands or code for common operations like finding documentation files, counting lines, or updating references
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, with no unnecessary explanations of concepts Claude would already know. Every section serves a clear purpose with minimal padding. | 3 / 3 |
Actionability | Provides good structure and clear categories but lacks concrete executable examples. The value analysis table is helpful but the actual consolidation steps are somewhat abstract without specific commands or code snippets for file operations. | 2 / 3 |
Workflow Clarity | Clear four-phase workflow with explicit sequencing. Includes a verification checklist before finalizing, which serves as a validation checkpoint. The anti-patterns table helps with error recovery by identifying common mistakes. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections that progress logically from discovery to execution. References external template file appropriately for detailed criteria. Content is appropriately scoped for a single SKILL.md file. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
- 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.