← Back to Skills
CopywritingContent CreationPlatinum

Create clear and reliable technical documentation for developers.

Technical Documentation Writer

Diataxis, OpenAPI, Docs-as-Code

intermediatev5.0

Best for

  • Creating comprehensive API reference documentation with OpenAPI specifications
  • Writing step-by-step SDK integration tutorials for developer onboarding
  • Building README files that get developers from zero to working code
  • Documenting microservices architecture with runbooks and operational guides

What you'll get

  • Complete API reference section with endpoint descriptions, request/response examples, error codes, and authentication requirements
  • Step-by-step tutorial with working code samples that takes a developer from setup to successful integration
  • Comprehensive README with clear installation, usage examples, and troubleshooting sections structured for quick scanning
Expects

Clear description of the technical system, target developer audience, and specific documentation type needed (tutorial, reference, how-to, or explanation).

Returns

Structured technical documentation following Diataxis framework with proper information architecture, code examples, and developer-focused clarity.

What's inside

You are a Technical Documentation Writer. You transform product specifications, APIs, systems, and concepts into clear, actionable documentation that developers can use immediately. - **Classify before writing**: Every piece of documentation fits into one of four types (Tutorial, How-To, Reference, ...

Covers

What You Do DifferentlyMethodologyWatch ForOutput Format Format
Not designed for ↓
  • ×Marketing copy or sales documentation for technical products
  • ×End-user help documentation or customer support articles
  • ×Legal compliance documentation or regulatory writing
  • ×Academic research papers or white papers

SupaScore

90.68
Research Quality (15%)
9.25
Prompt Engineering (25%)
9.15
Practical Utility (15%)
8.85
Completeness (10%)
9.5
User Satisfaction (20%)
9.05
Decision Usefulness (15%)
8.7

Evidence Policy

Standard: no explicit evidence policy.

technical-writingapi-documentationdeveloper-docsdiataxisdocs-as-codetutorialsreadmechangelogopenapiinformation-architecturerunbooksdeveloper-experiencestyle-guide

Research Foundation: 8 sources (4 official docs, 1 web, 3 industry frameworks)

This skill was developed through independent research and synthesis. SupaSkills is not affiliated with or endorsed by any cited author or organisation.

Version History

v5.03/25/2026

v5.5 distilled from v2 via Claude Sonnet

v2.02/26/2026

Pipeline v4: rebuilt with 3 helper skills

v1.0.02/15/2026

Works well with

Need more depth?

Specialist skills that go deeper in areas this skill touches.

Common Workflows

Complete API Documentation Pipeline

Design API structure, create comprehensive documentation, then produce specific API reference materials

API Design Architecttechnical-documentation-writerAPI Documentation Writer

© 2026 Kill The Dragon GmbH. This skill and its system prompt are protected by copyright. Unauthorised redistribution is prohibited. Terms of Service · Legal Notice