Write software documentation structured by Diátaxis. Use when the user wants a tutorial, how-to guide, reference page, explanation doc, or user guide — "write docs", "document this", "we need a guide for X". Not for READMEs (write-readme) or docstrings (update-docstrings).
Add comprehensive documentation for the current code/feature and format it according to the ...; keywords: api, architecture, error. Use only on explicit request; skip in routine implementation discussions.
Use when a significant architecture decision that is hard to walk back is taken: the ADR template, what belongs there rather than in inline docs, and the never-delete-always-supersede rule.
Writes and reviews code documentation: dartdoc, JSDoc, Python docstrings, and implementation comments, with per-language conventions for Dart, Python, and TypeScript. Use when writing new code or features, documenting public APIs, improving existing docstrings or comments, or checking a change for missing or unhelpful documentation. Don't use for prose documents such as READMEs, design docs, or PR descriptions (use write-prose).
Manage Taiga wiki pages and documentation using MCP tools. Use when: creating wiki pages, updating documentation, managing wiki links and navigation, tracking wiki changes, organizing project documentation.
Produce and maintain the complete Markdown documentation set for an Odoo implementation - requirements, questions and decisions, fit-gap matrix, technical limitations, demo DB configuration log, project phases, detailed workflow explanations (why and how), step-by-step review guide and customization specifications - in the client's confirmed language(s).
Write, review, and audit code documentation to the standard the language and the project actually use — Python docstrings (PEP 257, Google, NumPy, reST), C and C++ comment blocks (Doxygen, kernel-doc), plus READMEs and API reference docs. Use this skill whenever the user asks to document code, add or fix docstrings or comments, explain a module so other developers can use it, write or refresh a README or API reference, check documentation coverage, or judge whether existing docs are still accurate — including short requests like "document this", "add comments here", "describe this module for the team", or handing over a file and asking what its docs are missing.
Use when writing, revising, reorganizing, or reviewing technical documentation — concept guides, feature docs, API references, developer-tool docs, tutorials, or docstrings that compile into user-facing docs. Covers both how to teach a single concept on one page and how to keep an entire documentation set coherent as it grows. Also covers short user-facing product text — UI copy, error messages, empty states, tooltips, and help text — which follows ASD-STE100 Simplified Technical English conventions (see "User-Facing Text"). Trigger whenever a task involves producing or improving end-user or developer-facing documentation, or when writing product strings a user will read. Not for README files (use crafting-effective-readmes), conversational walkthroughs of existing code or changes (use explain), or inline code comments.
824mo agoReviewMountCreate a free account to mount
Determines which PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires and where each is stored. Use when deciding documentation scope or creating or reviewing a technical document.
2393d agoReviewMountCreate a free account to mount
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.