Documentation Skills for AI Agents
Documentation skills produce written material that explains a system to a reader. The sub-topics here map to four reader needs: tutorials for learning by doing, how-to guides for finishing a known task, reference for looking up what exists and how it is invoked, and explanation for understanding why a system works the way it does. API docs and release notes sit alongside those, covering interfaces and version changes. Use the ranked list by matching your reader's need first, then your deliverable: a worked example, a set of steps, lookup material, or background reasoning. Read each skill's description to confirm it targets that need, and check whether it covers the format you must ship, such as endpoint and type descriptions or a version-to-version change summary.
8 to start with27 top options
Start with these.
Documentation splits by the reader's need: learn by doing, finish a task, look up a fact, or understand why something is the way it is.
These are the closest matches for this work. Start with the first one and open it to install.
- Rank 01View Agent SkillDirect
doc-coauthoring
OfficialGuide 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.
- Rank 02View Agent SkillDirect
wiki-architect
OfficialAnalyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or understand a project's architecture at a high level.
- Rank 03View Agent SkillDirect
documentation-and-adrs
NotableRecords decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
- Rank 04View Agent SkillDirect
golang-swagger
Golang OpenAPI/Swagger documentation with swaggo/swag: annotation comments, swag init code generation, framework integrations, security definitions, and struct tags.
34,105 · popularity - Rank 05View Agent SkillDirect
golang-documentation
Comprehensive documentation guide for Go projects covering godoc comments, README, CONTRIBUTING, CHANGELOG, Example tests, API docs, and llms.txt, with write and review modes.
37,233 · popularity - Rank 06View Agent SkillDirect
notion-research-documentation
OfficialResearch across Notion and synthesize into structured documentation; use when gathering info from multiple Notion sources to produce briefs, comparisons, or reports with citations.
- Rank 07View Agent SkillDirect
writing-guidelines
OfficialReview docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".
- Rank 08View Agent SkillDirect
docx
OfficialUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Explore 19 more Agent Skills
- Rank 09View Agent SkillPossible
design-doc-mermaid
Creates Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code, with design-document templates and GitHub wiki/Confluence guidance.
66,434 · popularity - Rank 10View Agent SkillPossible
wiki-llms-txt
OfficialGenerates llms.txt and llms-full.txt files for LLM-friendly project documentation following the llms.txt specification. Use when the user wants to create LLM-readable summaries, llms.txt files, or make their wiki accessible to language models.
Needs (stated): Docker
- Rank 11View Agent SkillPossible
domain-modeling
Builds and sharpens a project's domain model, challenging terminology and writing a CONTEXT.md glossary plus ADRs as decisions crystallise.
777,796 · popularity - Rank 12View Agent SkillPossible
writing-beats
Assembles raw material into a journey of beats, grounding each concept before a beat leans on it, with choose-your-own-adventure beat selection.
425,434 · popularity - Rank 13View Agent SkillPossible
writing-shape
Shapes raw material into an article paragraph by paragraph, establishing prerequisites and grounding concepts before each block leans on them.
424,940 · popularity - Rank 14View Agent SkillPossible
grill-with-docs
A relentless interview to sharpen a plan or design that also creates docs (ADRs and a glossary) as the conversation proceeds.
1,123,345 · popularity - Rank 15View Agent SkillPossible
research
Spins up a background agent to investigate a question against primary sources and write findings to a Markdown file with per-claim citations.
629,500 · popularity - Rank 16View Agent SkillPossible
writing-for-agents
Reference for writing documents an agent consumes: skills, AGENTS.md/CLAUDE.md, and pointed-to docs, covering context pointers, information hierarchy, and progressive disclosure.
381,976 · popularity - Rank 17View Agent SkillPossible
archify
Creates polished, validated architecture, workflow, sequence, data-flow, and lifecycle diagrams as explorable standalone HTML with inline SVG and export options.
140,157 · popularity - Rank 18View Agent SkillPossible
lark-doc
Notable飞书云文档（Docx / Wiki）内容操作：读取、创建、编辑文档，插入或下载图片附件，以及操作思维笔记。用户提供文档 URL/token（包括 doubao.com 的 /docx/、/wiki/）时使用；按 URL 路径/token 而非域名路由。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive；随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
750,729 · popularity - Rank 19View Agent SkillPossible
microsoft-docs
OfficialUnderstand Microsoft technologies by querying official documentation. Use whenever the user asks how something works, wants tutorials, needs configuration options, limits, quotas, or best practices for any Microsoft technology (Azure, .NET, M365, Windows, Power Platform, etc.)—even if they don't mention "docs." If the question is about understanding a concept rather than writing code, this is the right skill.
- Rank 20View Agent SkillPossible
source-driven-development
Grounds implementation decisions in official documentation, detecting stack versions, fetching the relevant docs page, and citing sources for verified code.
Needs (stated): Python
44,922 · popularity - Rank 21View Agent SkillPossible
gws-docs
NotableRead and write Google Docs.
55,914 · popularity - Rank 22View Agent SkillPossible
firecrawl-developer-index
NotableSearch issues, merged pull requests, READMEs, and documentation. Use when the question is how a library or API behaves, what an error means, or whether a bug was fixed; prefer this over a general web page.
- Rank 23View Agent SkillPossible
openai-docs
OfficialUse when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; use OpenAI docs MCP tools for non-Codex docs questions, use the Codex manual helper first for broad Codex self-knowledge, and restrict fallback browsing to official OpenAI domains.
- Rank 24View Agent SkillPossible
retrieving-developer-knowledge
Official>- Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI/Gemini, Android, Chrome, Web, Flutter, Go, Firebase, and other Google developer platforms. Integrates with the Developer Knowledge MCP server (search_documents, get_documents, answer_query) or the Developer Knowledge REST API fallback. Use when searching for gcloud CLI commands, API syntax, IAM permissions, official documentation, architectural comparisons, or product choice overviews. Don't use for local filesystem lookups or non-Google documentation.
- Rank 25View Agent SkillPossible
Nia
Indexes and searches code repositories, documentation, papers, datasets, Slack, and Drive with Nia AI, including Oracle research and dependency analysis.
55,461 · popularity - Rank 26View Agent SkillPossible
remotion-docs
NotableSearch Remotion documentation
- Rank 27View Agent SkillPossible
lark-wiki
Manages Feishu knowledge spaces, members, and document nodes: creating and querying spaces, organizing node hierarchies, and moving or copying nodes.
748,896 · popularity
What this topic covers
Each sub-topic groups Agent Skills for a specific situation.
- Tutorials
- A lesson that takes a newcomer through a worked example so they can learn by doing.
- How-to guides
- Steps to accomplish a specific job the reader already knows they want.
- Reference
- Accurate lookup material: what exists, what it is called, and how it is invoked.
- Explanation
- Background and reasoning so the reader understands the system, not just how to operate it.
- API docs
- Machine and human descriptions of interfaces: endpoints, types, and examples.
- Release notes
- What changed between versions and what a reader must do about it.
Frequently asked questions
- How do I choose between a tutorial skill and a how-to guide skill?
- A tutorial takes a newcomer through a worked example so they learn by doing. A how-to guide gives steps to accomplish a specific job the reader already knows they want. Pick based on whether your reader is new to the subject or already knows the goal and needs the procedure.
- What belongs in reference versus explanation?
- Reference is accurate lookup material: what exists, what it is called, and how it is invoked. Explanation is background and reasoning so the reader understands the system, not just how to operate it. If the reader needs a fact, use reference; if they need the why, use explanation.
- How is the ranked list ordered?
- The list is ranked by observed search demand, with direct matches to the topic placed first and a cap on any single publisher. Work down the list and stop at the first skill whose description matches your reader's need and required deliverable.
How to install an Agent Skill
Start with the first skill on this page. Claude Code reads a SKILL.md once it is in the skills directory:
- Claude Code — copy the SKILL.md for doc-coauthoring into ~/.claude/skills/doc-coauthoring/ for yourself, or .claude/skills/doc-coauthoring/ to share it with a project.
- From the registry — run npx skills add anthropics/skills@doc-coauthoring.
- Or download doc-coauthoring from its source and place that SKILL.md in the directory above.
How to choose Check the source and the skill’s own instructions before you install. Official and Notable describe where a skill comes from.