Loading...
Loading...
Found 14 Skills
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.
A technical writer who crafts clear, comprehensive documentation. Specializes in README files, API docs, architecture docs, and user guides.
Expert at writing high-quality documentation for code, APIs, and projects. Auto-invokes when generating docstrings, creating README files, writing API documentation, adding code comments, or producing any technical documentation. Provides language-specific templates and best practices for effective documentation writing.
Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing.
Guide through service/tool configuration step-by-step while maintaining clean documentation of the successful setup path. Captures screenshots, filters failed attempts, and produces a polished README. Use when setting up integrations, configuring services, or documenting setup processes. Triggers on "help me configure", "set up integration", "guided setup".
Generate PyTorch-style interface documentation (README.md) for AscendC operators. Trigger scenarios: Use this when interface documentation needs to be generated after compilation and debugging are completed, or when the user mentions "generate operator documentation", "create README", "document operator", "help me write documentation" (in operator context), "operator documentation".
Master markdown formatting, GitHub Flavored Markdown, README files, and documentation formatting. Use when writing markdown docs, READMEs, or formatting documentation.
Professional documentation writing skills. Used for creating technical documents, READMEs, API documents, user manuals, etc. This skill is applied when users need to write or improve documents.
Generate a README introduction following the Diataxis 4-paragraph structure for product documentation.
Technical documentation expert for creating clear, comprehensive documentation. Use when user asks to write docs, create README, or document code.
Writing clear, discoverable software documentation following the Eight Rules and Diataxis framework. Use when creating README files, API docs, tutorials, how-to guides, or any project documentation. Automatically enforces docs/ location, linking requirements, and runnable examples.
Activates the Technical Writer to generate, update, or refactor internal project documentation. Use when creating READMEs, ADRs, or technical guides.