docs-change
Simplifies and maintains human-facing project documentation.
Install
mkdir -p .claude/skills/docs-change && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12628" && unzip -o skill.zip -d .claude/skills/docs-change && rm skill.zipInstalls to .claude/skills/docs-change
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.
Use for README, Markdown, and human-facing documentation edits so docs stay concise, audience-appropriate, and scoped to the request.Key capabilities
- →Edit README, Markdown, and human-facing documentation
- →Preserve document purpose, audience, tone, and detail level
- →Make only requested documentation changes
- →Prefer concise useful wording over exhaustive technical detail
- →Verify factual claims against relevant source files
- →Perform lightweight verification of documentation changes
How it works
The skill edits documentation by adhering to rules that prioritize conciseness, audience appropriateness, and scope, ensuring that changes align with the document's original intent.
Inputs & outputs
When to use docs-change
- →Updating README files
- →Refining markdown docs
- →Concise documentation edits
About this skill
Docs Change
Core rule
Preserve the document's purpose, audience, tone, and level of detail.
A README is the project's front door:
- explain what the project is
- help a reader understand what it does
- provide only the setup information needed to get started
- link or defer to deeper technical material when needed
Do not turn concise human-facing docs into architecture manuals, changelogs, or exhaustive implementation references unless explicitly requested.
Editing rules
- Make only the requested documentation change.
- Keep nearby wording consistent, but do not broaden scope.
- Prefer concise useful wording over exhaustive technical detail.
- Do not add new sections, large rewrites, or speculative content unless the issue explicitly asks for them.
- Verify factual claims against the relevant source file when needed.
Verification
For docs-only work, prefer lightweight verification:
- inspect the diff for only the intended files
- confirm no unrelated files changed
- run heavier checks only if the issue or changed files justify them
When not to use it
- →When the request involves large rewrites or speculative content not explicitly asked for
- →When the documentation needs to be an architecture manual or exhaustive implementation reference
- →When the changes are to non-documentation files
Limitations
- →Does not add new sections, large rewrites, or speculative content unless explicitly requested
- →Focuses on preserving the document's original purpose and audience
- →Verification prefers lightweight checks unless justified by the issue or changed files
How it compares
This skill provides a disciplined approach to documentation edits, preventing bloat and maintaining focus, unlike unstructured edits that might introduce unnecessary technical detail or broaden scope.
Compared to similar skills
docs-change side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| docs-change (this skill) | 0 | 3mo | No flags | Beginner |
| 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.
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/.