SkillHub

Skills anthropics knowledge-work-plugins

documentation

Use it when:
You ask for a README, API reference, runbook, architecture doc or onboarding guide.
It gives:
A short checklist of the sections each of those five document types should have.
Principles:
Write for the reader, put the most useful information first, show code examples, commands and screenshots, keep docs current, link instead of copying.
Unlike doc-coauthoring:
That one drafts a doc with you section by section and tests it on a fresh reader; this one is a one-page checklist with no templates or steps.
Part of:
The engineering plugin of Anthropic's knowledge-work plugins.

TL;DR

A short reference the agent picks up when you ask it to document something. For each document type it lists what to cover. A README says what the project is and why it exists, gets you to a first success in under five minutes, then covers configuration, usage and contributing. API docs give endpoints with request and response examples, authentication, error codes, rate limits, pagination and SDK examples. A runbook says when to use it, what access you need, the steps, how to roll back and who to escalate to. An architecture doc covers context and goals, a high-level design with diagrams, key decisions and trade-offs, and data flow. An onboarding guide covers environment setup, how the key systems connect, common tasks and who to ask. Five principles apply to all of them.

Summarizes the skill at ab4cb1c.

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill documentation

skills.sh pageSource on GitHubAll skills from anthropics/knowledge-work-plugins

Total Downloads
10,500 on skills.sh, Nov 9, 2026
Repo stars
35,234 anthropics/knowledge-work-plugins
First seen
Feb 24, 2026 on skills.sh
Weekly Downloads
135
-36% over the 8 weeks to Nov 9
Weekly values
Week toInstalls
Sep 21210
Sep 28191
Oct 5136
Oct 12134
Oct 19152
Oct 26145
Nov 2135
Nov 9135
Category
category:writing

Articles, docs, internal comms, research write-ups and prose that doesn't read as generated.
Type
type:guidelines

Knowledge and rules the agent applies while it works: best practices, design principles, API references.
Effect
effect:none

Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code.
Needs
needs:none

Instructions only. Works in any agent that supports skills.
Publisher
by:official

A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates.
Topics
docs-writingwriting

SKILL.md

From anthropics/knowledge-work-plugins at ab4cb1c. Checked daily, last changed Nov 6, 2026.

Frontmatter
name: documentation
description: Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.

Technical Documentation

Write clear, maintainable technical documentation for different audiences and purposes.

Document Types

README
  • What this is and why it exists
  • Quick start (< 5 minutes to first success)
  • Configuration and usage
  • Contributing guide
API Documentation
  • Endpoint reference with request/response examples
  • Authentication and error codes
  • Rate limits and pagination
  • SDK examples
Runbook
  • When to use this runbook
  • Prerequisites and access needed
  • Step-by-step procedure
  • Rollback steps
  • Escalation path
Architecture Doc
  • Context and goals
  • High-level design with diagrams
  • Key decisions and trade-offs
  • Data flow and integration points
Onboarding Guide
  • Environment setup
  • Key systems and how they connect
  • Common tasks with walkthroughs
  • Who to ask for what

Principles

  1. Write for the reader — Who is reading this and what do they need?
  2. Start with the most useful information — Don't bury the lede
  3. Show, don't tell — Code examples, commands, screenshots
  4. Keep it current — Outdated docs are worse than no docs
  5. Link, don't duplicate — Reference other docs instead of copying