Consolidate redundant documentation while preserving 100% of valuable content.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondocs-cleanerExecute the skills CLI command in your project's root directory to begin installation:
Fetches docs-cleaner from daymade/claude-code-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate docs-cleaner. Access via /docs-cleaner in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
4
total installs
4
this week
784
GitHub stars
0
upvotes
Run in your terminal
4
installs
4
this week
784
stars
Consolidate redundant documentation while preserving 100% of valuable content.
Critical evaluation before deletion. Never blindly delete. Analyze each section's unique value before proposing removal. The goal is reduction without information loss.
For each document, create a section-by-section analysis table:
| Section | Lines | Value | Reason |
|---|---|---|---|
| API Reference | 25 | Keep | Unique endpoint documentation |
| Setup Steps | 40 | Condense | Verbose but essential |
| Test Results | 30 | Delete | One-time record, not reference |
Value categories:
See references/value_analysis_template.md for detailed criteria.
Propose target structure:
Before: 726 lines (3 files, high redundancy)
After: ~100 lines (1 file + reference in CLAUDE.md)
Reduction: 86%
Value preserved: 100%
Before finalizing, confirm preservation of:
| Pattern | Problem | Solution |
|---|---|---|
| Blind deletion | Loses valuable information | Section-by-section analysis first |
| Keeping everything | No reduction achieved | Apply value criteria strictly |
| Multiple sources of truth | Future divergence | Single authoritative location |
| Orphaned references | Broken links | Update all references after consolidation |
A successful cleanup produces:
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
daymade/claude-code-skills
daymade/claude-code-skills
langchain-ai/deepagents
upstash/context7
zrong/skills
google-gemini/gemini-cli
docs-cleaner reduced setup friction for our internal harness; good balance of opinion and flexibility.
docs-cleaner fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: docs-cleaner is focused, and the summary matches what you get after install.
docs-cleaner has been reliable in day-to-day use. Documentation quality is above average for community skills.
docs-cleaner reduced setup friction for our internal harness; good balance of opinion and flexibility.
docs-cleaner has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend docs-cleaner for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in docs-cleaner — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: docs-cleaner is focused, and the summary matches what you get after install.
docs-cleaner reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 67