Document

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.

155 stars 30 forksWriting & Content Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add serpro69/claude-toolbox

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add serpro69/claude-toolbox --skill document
Manual install
git 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/document ~/.claude/skills/document

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Documentation Process

## Conventions

- **Read capy knowledge base conventions** at [shared-capy-knowledge-protocol.md](shared-capy-knowledge-protocol.md).
- **Read profile detection** at [shared-profile-detection.md](shared-profile-detection.md). When an active profile contributes a `document/` subdirectory (e.g., `${TOOLBOX_PLUGIN_ROOT}/profiles/k8s/document/`), its `index.md` lists a doc rubric — required topics the documentation for that artifact type must cover. See the Workflow below for the load order.

## Workflow

**Mandatory order — instructions before action.** The flow below is strictly sequential. Do not read feature-tree content, write, or edit documentation files until the shared protocols and all resolved profile content are in context. Bounded signal inspection for profile detection is the only content-read exception.

Read the shared protocols in Conventions before the steps below, even when the invocation ultimately needs no edits.

1. **Minimal-scope listing.** List the feature directory (filenames and metadata only — no file-content reads). This is the input profile detection needs, and nothing more; content-level reading happens after profile content is loaded.
2. **Detect active profiles.** Run the `shared-profile-detection.md` procedure against the filename list from Step 1.
Read the full skill on GitHub

Details

Skill name
document
Path
klaude-plugin/skills/document/SKILL.md
License
Apache-2.0
Repo updated
18 November 2026

FAQ

What does the Document skill do?

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.

How do I install the Document 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 Document 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

155

serpro69/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.

Productivity & NotesIn 1 list30

Chain of Verification

155

serpro69/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.

AI, LLMs & AgentsIn 1 list30

Clarify Docs

155

serpro69/claude-toolbox

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.

Writing & ContentIn 1 list30

Linkedin Post Writer

116

aakashg/pm-claude-skills

Use when the user asks to write, draft, or rewrite a LinkedIn post, turn notes or an article into a LinkedIn post, or fix a hook that is not landing. Do NOT use for X/Twitter threads, newsletters, or blog posts — those need different length and hook rules.

Writing & Content35

Design

155

serpro69/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.

Writing & ContentIn 1 list30

Merge Docs

155

serpro69/claude-toolbox

Compare and merge two design docs for the same feature into a single source of truth. Use when you have competing or complementary design/implementation docs (e.g. from separate design runs) that need reconciling into one unified document.

Writing & ContentIn 1 list30

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.