Best skills for: Auto documentation
When automating documentation with AI coding assistants like Cursor, Copilot, or Claude Code, the key is choosing skills that add real value rather than generating fluff. For this task, focus on skills that refine and validate existing content. 'Enrich a Documentation Section' works best when you provide a code snippet or API signature and ask for expanded explanations, edge cases, or usage examples—this turns a stub into production-ready docs. Another strong pick is 'Specification Document Reviewer', which checks your documentation against technical requirements or code behavior, catching inconsistencies early. The most common pitfall is being too vague: generic prompts yield generic output. Always specify the target format (e.g., Markdown, reStructuredText) and the intended audience (end users vs. maintainers). These skills shine when combined—first enrich a section, then review it against specs. Avoid over-automation; always review AI-generated docs for accuracy.
24 skills selected
Technical Documentation
Documentation
Provides best practices and templates for various documentation types including READMEs, API references, code comments, and architecture diagrams. Helps maintain consistency and clarity when creating or improving project documentation, especially for open-source projects or APIs.
Documentation Writer
Documentation
Generates API documentation, README files, and updates docstrings. Follows standards like Google, NumPy, or Sphinx. Helpful for maintaining clear, concise, and up-to-date code documentation.
Enrich a Documentation Section
Documentation
Helps enrich thin documentation sections that only show a signature and toy example without explaining the reasoning or use-cases. Provides a five-part expansion pattern to add motivation, contrast with alternatives, and a realistic example, making it easier for readers to understand when and why to use the API.
Phonely Docs Agent Contract
Documentation
Guidelines for AI agents updating Phonely documentation. Emphasizes source traceability, audience voice, and separation of behavior, knowledge, and tools.
Ark Documentation with Diataxis
Documentation
Provides guidance for structuring Ark documentation using the Diataxis framework (Tutorials, How-to Guides, Core Concepts, Reference). Helps decide where content belongs, review documentation PRs, and restructure existing docs. Use this skill when creating new documentation or ensuring a consistent, task-oriented layout for different audiences.
Technical Documentation Research
Documentation
Guides searching and fetching authoritative technical documentation, API references, and implementation patterns. Helps when exploring unfamiliar frameworks, version-specific needs, or best practices for technical decisions.
Documentation Claim Check
Documentation
Read-only audit of whether claims in public docs are supported by evidence. No commands run, no fixes written.
Document Indexer
Documentation
Scans YAML frontmatter from all markdown files in the docs/ directory to produce a structured overview of available documentation without loading full files. Use this at the start of a session or when you need to quickly find relevant specs, plans, and context.
Knowledge Base Capture
Documentation
Capture architectural decisions, non-obvious bugs, and other critical findings into the project knowledge base.
Technical Documentation
Documentation
Creates and maintains comprehensive technical documentation: API docs, READMEs, ADRs, changelogs, code comments, user and developer guides.
Documentation Maintenance
Documentation
This skill provides a structured workflow for updating project documentation including CLAUDE.md, README, and CHANGELOG. It walks through phases like inventorying existing docs, analyzing git history for needed changes, optimizing for AI readability, and ensuring cross-document consistency. Use it when synchronizing documentation with code changes or improving documentation effectiveness for AI coding agents.
Scaffold and validate RFCs
Documentation
Scaffold and validate ArenaQuest RFCs against a house standard: numbered files, metadata headers, canonical sections, and README index rows.
Create ADR
Documentation
Record an architecture decision at the moment it's made, including context, options considered, decision, and consequences in docs/decisions/.
KDoc Documentation Writer
Documentation
Writes concise KDoc documentation for Kotlin classes and functions, focusing on short summaries without metadata or variable documentation. Helps when adding KDoc to Kotlin files while skipping private or obvious members.
Morphir Knowledge Base Manager
Documentation
Manages the Morphir knowledge base under kb/: OKF bundles, concept documents, SQLite index, intent lifecycle and Decision Records via the morphir kb CLI.
Sync Multilingual README Files
Documentation
Synchronizes English (README.md) and Chinese (README_ZH.md) documentation by translating new or changed sections between the two files. Preserves code blocks, formatting, and technical term consistency. Useful for maintaining bilingual documentation in multi-language projects.
Project Knowledge Manager
Documentation
Maintains a living knowledge base in .knowledge/ directory with focused markdown files about the codebase, architecture, and design decisions.
Knowledge-Driven Development
Documentation
Record decisions and meta-reflection after features with trade-offs or architectural choices. Captures why and surfaces session friction as chat output only.
Diataxis Documentation Framework
Documentation
Create comprehensive, user-focused documentation using the Diataxis framework. Identify the right documentation type (tutorials, how-to guides, references, explanations) and apply best practices for each.
Beautify GitHub README
Documentation
Redesign GitHub README pages or create SVG assets like heroes, badges, and diagrams. Clarifies full-readme vs asset-only scope.
Update Dockerman Version
Documentation
Updates Dockerman version with changelog, configuration files and README badges in MDX format.
ADR Decisions
Documentation
Draft and gate Architecture Decision Records when changes are decision-worthy. Machine drafts; human approves.
Evidence-Driven README Optimization
Documentation
Creates or improves a Chinese-first README from repository facts, with every command and feature traceable to manifest and source files.
Prepare Changelog for Release
Documentation
Updates the CHANGELOG.md file by replacing the [Unreleased] section with the current plugin version and date, then adds a new empty [Unreleased] section. Use when finalizing a release to prepare the changelog entries.
How to choose
- How are these skills selected?
- An algorithm picks them among the published skills that match this page's criteria, such as category, tags or compatible tools. It ranks them by the quality score a language model gave them. On ranking pages, it also weighs GitHub stars and the security rating. Nobody reviews them one by one.
- What do the security ratings mean?
- A language model reads the SKILL.md file, without running it, and gives it a rating. Safe means it sees no meaningful execution risk. Caution means the skill uses powerful tools such as bash, docker or the network for a legitimate purpose. Risky means it asks for destructive actions, for secrets to be sent out, or for obfuscated code to run; a skill rated Risky is never published. The rating does not replace your own reading of the file.
- How do I install a skill?
- Open any skill page and follow its install instructions for your tool — Claude Code, Cursor or Copilot. Each skill lists the exact steps so you can get it running in a couple of minutes.