skills.rest
dzackgarza
dzackgarzaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-documentation

Rewrite rough technical drafts into concise, structured documentation.

1|Updated Feb 24, 2026
Search Tags:#documentation#writing#editing#style#clarity#brevity#strunk-white
One-click install
npx skills add https://github.com/dzackgarza/ai --skill writing-documentation-dzackgarza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-documentation
Source: https://github.com/dzackgarza/ai/tree/main/opencode/skills/writing-documentation
Command: npx skills add https://github.com/dzackgarza/ai --skill writing-documentation-dzackgarza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps technical writers produce concise, clear documentation by applying Strunk & White's principles to technical writing tasks, improving reader comprehension and reducing noise.

Core Features & Use Cases

  • Guides writing and improving documentation using established style rules
  • Enables consistent structure and tone across READMEs, API docs, tutorials, and architecture docs
  • Supports iterative editing workflows with checklists and quality guidance for both new and existing docs

Quick Start

Describe a draft document you want improved, and I will rewrite it for clarity and brevity following Strunk & White principles.

Frequently Asked Questions about writing-documentation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve technical documentation clarity and readability?▼

Technical documentation clarity improves by applying Strunk & White principles to enforce active voice, concrete language, and minimal wording. This approach converts rough drafts into well-structured text, reducing noise and enhancing reader comprehension across READMEs and guides.

What is the best way to rewrite a rough API guide for brevity?▼

The best way to rewrite an API guide for brevity is converting verbose drafts into precise text using established style rules. This process eliminates unnecessary wording while maintaining technical accuracy, outputting an improved version of the original document with consistent tone and structure.

How do I edit a README to use active voice and concrete language?▼

Editing a README to use active voice and concrete language involves applying Strunk & White principles to the draft. This process enforces minimal wording and precise phrasing, serving as a drop-in improved version of the original document with enhanced clarity.

Does technical writing style guidance work for both new and existing docs?▼

Technical writing style guidance works for both new and existing docs by supporting iterative editing workflows with checklists and quality guidance. It applies Strunk & White principles to ensure consistent structure, active voice, and readability across all documentation types.

Related Skills

Explore More Content & Communication Skills→
garethdainegarethdaine

editor

Edit and proofread written content for grammar, clarity, and style.

Community
Intermediate
nksethnkseth

code-documenter

Generate and validate inline documentation, API specs, and developer guides from source code.

Community
Advanced
AJBcodingAJBcoding
4

moai-cc-claude-md

Generate structured Markdown documentation with templates and cross-references.

Community
Advanced
Objective-ArtsObjective-Arts

editing

Edit technical writing for clarity, conciseness, and active voice.

Official
Basic