agentskills.codes
DO

docs-cleaner

by daymadeWritingSource

Merges duplicate documentation files to improve clarity and reduce project clutter.

DocumentationMarkdown

Install

mkdir -p .claude/skills/docs-cleaner && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2818" && unzip -o skill.zip -d .claude/skills/docs-cleaner && rm skill.zip

Installs to .claude/skills/docs-cleaner

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

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.
448 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • →Identify documentation files covering a specific topic
  • →Map content overlap between multiple documents
  • →Create section-by-section value analysis tables
  • →Propose target structure for consolidated documentation
  • →Update references in CLAUDE.md and README files
  • →Verify link integrity after file deletion

How it works

It performs a discovery phase to map overlaps, followed by a value analysis to categorize sections as keep, condense, or delete. Finally, it executes the consolidation and updates all internal references.

Inputs & outputs

You give it
Multiple documentation files with redundant content
You get back
A single consolidated document and a value analysis report

When to use docs-cleaner

  • →Merging duplicate readme files
  • →Reducing documentation sprawl
  • →Consolidating project wikis

About this skill

Documentation Cleaner

Consolidate redundant documentation while preserving 100% of valuable content.

Core Principle

Critical evaluation before deletion. Never blindly delete. Analyze each section's unique value before proposing removal. The goal is reduction without information loss.

Workflow

Phase 1: Discovery

  1. Identify all documentation files covering the topic
  2. Count total lines across files
  3. Map content overlap between documents

Phase 2: Value Analysis

For each document, create a section-by-section analysis table:

SectionLinesValueReason
API Reference25KeepUnique endpoint documentation
Setup Steps40CondenseVerbose but essential
Test Results30DeleteOne-time record, not reference

Value categories:

  • Keep: Unique, essential, frequently referenced
  • Condense: Valuable but verbose
  • Delete: Duplicate, one-time, self-evident, outdated

See references/value_analysis_template.md for detailed criteria.

Phase 3: Consolidation Plan

Propose target structure:

Before: 726 lines (3 files, high redundancy)
After:  ~100 lines (1 file + reference in CLAUDE.md)
Reduction: 86%
Value preserved: 100%

Phase 4: Execution

  1. Create consolidated document with all valuable content
  2. Delete redundant source files
  3. Update references (CLAUDE.md, README, imports)
  4. Verify no broken links

Value Preservation Checklist

Before finalizing, confirm preservation of:

  • Essential procedures (setup, configuration)
  • Key constraints and gotchas
  • Troubleshooting guides
  • Technical debt / roadmap items
  • External links and references
  • Debug tips and code snippets

Anti-Patterns

PatternProblemSolution
Blind deletionLoses valuable informationSection-by-section analysis first
Keeping everythingNo reduction achievedApply value criteria strictly
Multiple sources of truthFuture divergenceSingle authoritative location
Orphaned referencesBroken linksUpdate all references after consolidation

Output Artifacts

A successful cleanup produces:

  1. Consolidated document - Single source of truth
  2. Value analysis - Section-by-section justification
  3. Before/after metrics - Lines reduced, value preserved
  4. Updated references - CLAUDE.md or README with pointer to new location

When not to use it

  • →When documentation is already a single source of truth
  • →When files cover entirely unrelated topics

Prerequisites

Access to all documentation filesreferences/value_analysis_template.md

Limitations

  • →Requires manual review of the value analysis table
  • →Does not automatically rewrite content, only consolidates

How it compares

Unlike manual merging, this skill uses a structured value analysis table to justify every deletion and ensure 100% of valuable content is preserved.

Compared to similar skills

docs-cleaner side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
docs-cleaner (this skill)12moNo flagsIntermediate
ml-paper-writing486moReviewAdvanced
docs-review107moNo flagsBeginner
claude-md-improver216moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

More by daymade

View all by daymade →

ppt-creator

daymade

Create professional slide decks from topics or documents. Generates structured content with data-driven charts, speaker notes, and complete PPTX files. Applies persuasive storytelling principles (Pyramid Principle, assertion-evidence). Supports multiple formats (Marp, PowerPoint). Use for presentations, pitches, slide decks, or keynotes.

75110

macos-cleaner

daymade

Analyze and reclaim macOS disk space through intelligent cleanup recommendations. This skill should be used when users report disk space issues, need to clean up their Mac, or want to understand what's consuming storage. Focus on safe, interactive analysis with user confirmation before any deletions.

1631

qa-expert

daymade

This skill should be used when establishing comprehensive QA testing processes for any software project. Use when creating test strategies, writing test cases following Google Testing Standards, executing test plans, tracking bugs with P0-P4 classification, calculating quality metrics, or generating progress reports. Includes autonomous execution capability via master prompts and complete documentation templates for third-party QA team handoffs. Implements OWASP security testing and achieves 90% coverage targets.

1427

repomix-unmixer

daymade

Extracts files from repomix-packed repositories, restoring original directory structures from XML/Markdown/JSON formats. Activates when users need to unmix repomix files, extract packed repositories, restore file structures from repomix output, or reverse the repomix packing process.

524

teams-channel-post-writer

daymade

Creates educational Teams channel posts for internal knowledge sharing about Claude Code features, tools, and best practices. Applies when writing posts, announcements, or documentation to teach colleagues effective Claude Code usage, announce new features, share productivity tips, or document lessons learned. Provides templates, writing guidelines, and structured approaches emphasizing concrete examples, underlying principles, and connections to best practices like context engineering. Activates for content involving Teams posts, channel announcements, feature documentation, or tip sharing.

591

twitter-reader

daymade

Fetch Twitter/X post content by URL using jina.ai API to bypass JavaScript restrictions. Use when Claude needs to retrieve tweet content including author, timestamp, post text, images, and thread replies. Supports individual posts or batch fetching from x.com or twitter.com URLs.

552

You might also like

ml-paper-writing

davila7

Write publication-ready ML/AI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. Includes LaTeX templates, reviewer guidelines, and citation verification workflows.

4897

docs-review

metabase

Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.

1085

claude-md-improver

anthropics

Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project memory optimization".

2167

write-docs

tldraw

Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.

665

update-docs

vercel

This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.

2543

wiki-architect

microsoft

Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or understand a project's architecture at a high level.

1144

Search skills

Search the agent skills registry