Loading...
Loading...
Found 119 Skills
Write clear, comprehensive technical documentation. Use when creating specs, architecture docs, runbooks, or API documentation. Handles technical specifications, system design docs, operational guides, and developer documentation with industry best practices.
Expert technical writing guidelines for creating clear, in-depth developer tutorials and documentation with practical, implementable knowledge
A collection of technical writing rules to significantly improve the quality of your writing. Achieve professional writing quality by eliminating redundant expressions, avoiding repeated sentence endings, correctly distinguishing between kanji and hiragana, using active voice, and placing subjects and predicates close together, among other practices. This must be referenced for all tasks involving text output or generation. Applicable tasks include creating PR descriptions, writing technical documents, design documents, specifications, and procedure manuals, updating README/CLAUDE.md/Confluence pages, generating commit messages, summarizing survey results and specifications, outputting in Markdown, improving and reviewing existing text, etc. This skill is triggered by all requests involving text output, such as "write", "create", "compose", "summarize", "add to", "output", "improve", "review", "document", "create a PR", "output in Markdown", etc. Refer to this skill even for short instructions or implicit text generation tasks. Explicit mention of the skill name is not required.
Write clear technical documentation following Tenzir's style conventions. Use when writing or editing docs, README files, API documentation, user guides, changelog descriptions, or error messages. Also use when the user asks about writing style, tone, formatting, capitalization rules, inclusive language, or how to structure technical content — even if they don't mention "documentation" explicitly.
Write clear, engaging technical content from real experience. Use when writing blog posts, documentation, tutorials, or technical articles.
Guide for creating effective internal technical documentation (READMEs, ADRs, Contribution Guides). Use this skill when the user asks to write, refactor, or improve internal project documentation.
Use this skill when writing, reviewing, or structuring technical documentation for software projects. Triggers on API documentation, tutorials, architecture decision records (ADRs), runbooks, onboarding guides, README files, or any developer-facing prose. Covers documentation structure, writing style, audience analysis, and doc-as-code workflows for engineering teams.
The craft of communicating technical concepts clearly to developers. Developer communications isn't marketing—it's about building trust through transparency, accuracy, and genuine utility. The best devrel content helps developers solve real problems. This skill covers technical documentation, developer tutorials, API references, changelog writing, developer blog posts, and developer community engagement. Great developer communications treats developers as peers, not leads to convert. Use when "documentation, docs, tutorial, getting started, API reference, changelog, release notes, developer guide, devrel, developer relations, code examples, SDK docs, README, documentation, devrel, tutorials, api-docs, developer-experience, technical-writing, getting-started, changelogs" mentioned.
Technical documentation specialist for API docs, tutorials, architecture docs, and developer experienceUse when "documentation, docs, readme, tutorial, api docs, guide, changelog, comments, openapi, documentation, api-docs, tutorials, readme, openapi, swagger, developer-experience, technical-writing, ml-memory" mentioned.
Rewrite specified documents to remove AI-generated traces. Automatically select the most suitable humanization strategy (humanizer-zh / humanize-chinese / technical-writing), and iterate rewriting until the result meets the standard or reaches a maximum of 42 iterations. Suitable for de-AI processing of Chinese texts, including general articles, technical documents, academic papers, etc. Use when user says: "humanize this", "去AI味", "降AIGC", "人性化改写", "改成人话", "去除AI痕迹", "humanize document", "make text human-like", "去机器味", "降低AI率", "过AIGC检测"
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.