2.4K skills · sorted by relevance
Write and revise Chinese technical documentation using consistent spacing, punctuation, terminology, and structure. Includes README.md and API documentation templates, bilingual formatting examples, and a checklist for reviewing documents before publication.
Organize API documentation work from endpoint discovery to OpenAPI specifications, developer guides, and tested code examples. The workflow also covers interactive documentation, documentation sites, and maintenance, helping select the phases and supporting skills needed for a task.
Generate or update up to nine project documentation files using agents that inspect the code directly. Check documentation against the implementation, review existing files without writing changes, or explicitly regenerate all documentation.
Route broad requests about project documentation to a suitable specialist skill. When requested, run a read-only audit of document roles, local links, architecture decision indexes, and evidence references, reporting failures and items needing review.
Turn source code into project documentation, from a README with installation steps and examples to API references, architecture diagrams, developer guides, and changelogs. Match the scope and comment format to the project's size and programming language.
Generate and update API or project documentation, and flag inconsistencies between existing docs and current code. Schedule recurring maintenance and save the documentation approach for reuse in later work.
Maintain Cherry Studio documentation by checking it against source code, placing facts in appropriate files, and removing duplication. Review documentation affected by code changes and keep relevant English and Chinese counterparts aligned.
Creates software documentation using Diátaxis, a framework that separates learning, task instructions, reference information, and explanation. Clarifies the audience, goal, and scope, then proposes an outline before writing Markdown content consistent with existing documentation.
Maintain Composio's documentation site and record documentation decisions. Work on content, Fumadocs configuration, changelogs, automation prompts, and review guidance, including ADR-style records that capture decisions and their rationale.
Use when you need to generate or improve Java project documentation — including README.md files, package-info.java files, and Javadoc enhancements — through a modular, step-based interactive process that adapts to your specific documentation needs. This should trigger for requests such as Improve the code with documentation; Apply documentation; Refactor the code with documentation; Generate README or developer documentation for a Java project; Document Java APIs architecture or project workflows. Part of Plinth Toolkit
The English summary is being prepared. Showing the original description.
API Documentation Workflow workflow skill. Use this skill when the user needs API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
The English summary is being prepared. Showing the original description.
Create and review technical documentation alongside repository instructions for agents and contributors. The skill checks clarity, working procedures, documentation coverage, and consistency across languages, then provides updated drafts or findings with validation notes.
Compare release changes with project documentation, then update files such as README and CHANGELOG to reflect what shipped. The skill also checks architecture diagrams, maps missing documentation, and records remaining documentation work in the pull request.
Review, improve, rewrite, or draft Storybook documentation in /docs. Assess each page’s purpose, audience, structure, and examples, then make suitable edits or provide a content plan, with formatting checks after changes.
Find current documentation and code examples through the Context7 MCP server. Look up library setup, API usage, migration steps, and library-specific problems, using documentation for the requested version when available.
Configure MCP connections, which link AI agents to tools, for AWS documentation search and API access. Check existing settings, choose between documentation-only and full API access, verify available tools, and troubleshoot connection or credential problems.
Turn API code into documentation covering endpoints, inputs, authentication, responses, and errors. Add request examples in multiple languages and usage guides to help developers understand and start using the API.
Search automatically generated code documentation to check function parameters, class definitions, API details, and comments before making changes. Find relevant documents by meaning, exact keywords, or document type, then retrieve their full contents.
Find and retrieve official OpenAI documentation to answer API integration questions with source evidence. Check endpoint definitions, parameters, and documented limits, and receive setup guidance when the documentation connection is unavailable.
Organize Confluence documentation with clear page hierarchies, reusable templates, and access plans. Create and update pages, embed Jira reports, and audit existing content to identify outdated material and establish review responsibilities.
Keep project documentation aligned with recent code changes. Review commits since the last checkpoint, update affected guides and README files, and open a pull request for human review only when documentation needs correcting.
Create and maintain code comments, API specifications, documentation sites, and user guides. Apply consistent formats, document parameters and errors, validate code examples, and report which parts of the code have been documented.
Create and review technical documentation alongside repository instructions for agents and contributors. The skill checks clarity, working procedures, documentation coverage, and consistency across languages, then provides updated drafts or findings with validation notes.
Update Han plugin documentation so every skill, agent, guidance doc, index, and cross-reference is current and accurate. On a non-default branch, scopes the pass to entities the branch actually touched. On the default branch, performs a full documentation sweep across the whole plugin. Use when updating, refreshing, syncing, auditing, or verifying Han's docs after changing skills, agents, references, or top-level guidance — including "update the docs", "doc sweep", "refresh documentation", "audit the docs", "make sure the docs are current". This is a repository-maintenance skill for the Han repo itself, not a general documentation skill — use /project-documentation to document features in arbitrary projects, /han-release to cut a release (and update CHANGELOG), and /update-pr-description for PR bodies.
The English summary is being prepared. Showing the original description.