Clarify Docs
TRIGGER when: asked to clarify or improve existing documentation, PR drafts or issue descriptions, including URLs and pasted bodies. Saves results locally, grounded in requirements and source while preserving meaning. Not for requests to implement, fix or work on an issue, code, config, generic response brevity, or agent instructions. Explicit instruction or SKILL.md targets receive a /kk:implement suggestion without edits or invoking implementation.
Install
/plugin marketplace add serpro69/claude-toolboxThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add serpro69/claude-toolbox --skill clarify-docsgit clone --depth 1 https://github.com/serpro69/claude-toolbox.git /tmp/claude-toolbox
mkdir -p ~/.claude/skills
cp -r /tmp/claude-toolbox/klaude-plugin/skills/clarify-docs ~/.claude/skills/clarify-docsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Clarify Documentation, PR Drafts and Issue Descriptions Improve an existing document so its intended reader can understand the underlying work. Produce a local edit; success depends on comprehension and fidelity, with no document-length target. ## Inputs and boundaries Accept local documentation, PR or issue-description drafts, remote PR/issue URLs or pasted bodies, plus audience, purpose, requirements and source references. GitHub and Linear are examples, not required integrations. Examples: - `/kk:clarify-docs docs/configuration.md for service owners; use src/config/` - `/kk:clarify-docs docs/feat/wip/import/design.md for the implementing developer` - `/kk:clarify-docs pr-draft.md for repository reviewers; use the actual PR base/head` - `/kk:clarify-docs <PR URL>; save the revised body to docs/feat/wip/import/pr-draft.md` - `/kk:clarify-docs issue-draft.md; preserve the reported reproduction details` - `/kk:clarify-docs <issue URL>; save to docs/feat/wip/import/issue-draft.md` A directory permits discovery and selection, not a bulk rewrite. If selection is consequentially ambiguous, ask which artifact to edit. Related requirements and code may be read as evidence; only selected documentation may be changed. Edit an explicitly selected local draft in place. A capture of pasted/remote input is not automatically that draft. For remote or pasted input, use the caller's destination or name a local draft under the clearly established current feature
Details
- Skill name
clarify-docs- Repository
- serpro69/claude-toolbox
- Path
klaude-plugin/skills/clarify-docs/SKILL.md- License
- Apache-2.0
- Repo updated
- 18 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Clarify Docs skill do?
TRIGGER when: asked to clarify or improve existing documentation, PR drafts or issue descriptions, including URLs and pasted bodies. Saves results locally, grounded in requirements and source while preserving meaning. Not for requests to implement, fix or work on an issue, code, config, generic response brevity, or agent instructions. Explicit instruction or SKILL.md targets receive a /kk:implement suggestion without edits or invoking implementation.
How do I install the Clarify Docs skill?
Claude Code plugin: /plugin marketplace add serpro69/claude-toolbox. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Clarify Docs popular?
It lives in serpro69/claude-toolbox, which has 155 GitHub stars and 30 forks, and is included in 1 curated skill list.
Related skills
Brainstorm
155serpro69/claude-toolbox
TRIGGER when: asked to brainstorm, think through, explore, or pressure-test a technical idea or decision through conversation. Interviews adaptively, asks one question at a time, and closes with a chat recap. For technical products, architecture, infrastructure, tools, operations, and engineering workflows. Written design/specification and task-list requests belong to /kk:design; durable domain glossary/reference kits to /kk:model; implementation and fixes to /kk:implement. Not for nontechnical brainstorming.
Chain of Verification
155serpro69/claude-toolbox
Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.
Dependency Handling
155serpro69/claude-toolbox
TRIGGER when: adding or upgrading any dependency — library, SDK, framework, API, IaC API version (K8s/Terraform/Helm), CRD, or container image. Use BEFORE writing the call. Forces context7/capy lookup instead of guessing.
Design
155serpro69/claude-toolbox
TRIGGER when: asked to write or refine a technical design, PRD, specification, implementation plan, or task list, or resume an existing docs/feat/wip feature. Turns ideas and requirements into written design documents, implementation plans, and tasks in docs/feat/wip/ before coding. For conversational exploration without written planning, use /kk:brainstorm.
S4h Writing Worldbuilding
242human-avatar/skills-for-humanity
Audits a fictional world for internal consistency, texture, economy, and constraint-story alignment. Use when a world feels thin, generic, like a backdrop rather than a place people actually inhabit. Triggers: 'the world feels thin', 'worldbuilding', 'my world doesn't feel real', 'the setting is generic', 'world audit', 'the world feels like a backdrop'.
Document
155serpro69/claude-toolbox
After implementing a new feature or fixing a bug, make sure to document the changes. Use when writing documentation, after finishing the implementation phase for a feature or a bug-fix.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.