docs-maintenance
Standardizes documentation maintenance by removing duplicates and linking to canonical sources.
Install
mkdir -p .claude/skills/docs-maintenance && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10643" && unzip -o skill.zip -d .claude/skills/docs-maintenance && rm skill.zipInstalls to .claude/skills/docs-maintenance
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.
Review and edit iccDEV documentation for signal, accuracy, canonical ownership, and low-noise handoff.Key capabilities
- →Inventory duplicated documentation
- →Replace repeated detail with canonical links
- →Run whitespace and stale-reference checks
- →Delete duplicate files
How it works
Audits documentation for consistency and noise, replacing redundant content with links to canonical sources.
Inputs & outputs
When to use docs-maintenance
- →Removing duplicate documentation
- →Adding routing documentation
- →Reviewing documentation accuracy
- →Cleaning up technical docs
About this skill
Documentation Maintenance
Use this skill when reducing duplicated docs, adding routing docs, or reviewing documentation for accuracy.
Workflow
- Confirm the target branch and whether changes are local-only.
- Read
../../../docs/documentation-maintenance.mdfor canonical sources. - Inventory duplicated or stale content before editing.
- Preserve exact commands, paths, CMake options, executable names, and safety requirements.
- Replace repeated detail with links to canonical sources.
- Delete duplicate files only after moving unique content elsewhere.
- Run whitespace, local-link, ASCII, and stale-reference checks.
Harvest Rules
- Import reusable process, not repository-specific paths or private scratch locations.
- Prefer a short prompt or maintenance doc over another long reference file.
- Keep user-facing docs task-oriented; keep agent rules in
.github/.
References
../../../docs/documentation-maintenance.md../../prompts/reduce-doc-noise.prompt.md../../copilot-instructions.md
When not to use it
- →Modifying repository-specific paths
- →Editing private scratch locations
Prerequisites
Limitations
- →Requires manual inventory of stale content
- →Preserves exact commands and paths
How it compares
Focuses on centralizing technical references and reducing noise rather than just updating content.
Compared to similar skills
docs-maintenance side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| docs-maintenance (this skill) | 0 | 3mo | No flags | Intermediate |
| docs-write | 22 | 6mo | No flags | Beginner |
| content-research-writer | 15 | 10mo | No flags | Beginner |
| doc-coauthoring | 16 | 8mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by InternationalColorConsortium
View all by InternationalColorConsortium →You might also like
docs-write
metabase
Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).
content-research-writer
ComposioHQ
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
doc-coauthoring
anthropics
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
research-grants
davila7
Write competitive research proposals for NSF, NIH, DOE, and DARPA. Agency-specific formatting, review criteria, budget preparation, broader impacts, significance statements, innovation narratives, and compliance with submission requirements.
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.
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/.