copyedit-docs

Enforce active voice, concise phrasing, and consistent terminology in technical documentation.

5|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/sambeau/kanbanzai --skill copyedit-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copyedit-docs
Source: https://github.com/sambeau/kanbanzai/tree/main/.kbz/skills/copyedit-docs
Command: npx skills add https://github.com/sambeau/kanbanzai --skill copyedit-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams ensure technical documentation is clear, concise, and consistent by enforcing active voice, reducing wordiness, and standardizing terminology.

Core Features & Use Cases

  • Active voice enforcement across API references, guides, release notes, and other docs.
  • Punctuation hygiene and sentence-length optimization to improve readability.
  • Consistency checks for terminology, style, and formatting across multiple documents and teams.
  • Use Case: Take a draft developer guide and polish it into publish-ready content that meets your style guidelines.

Quick Start

Paste your draft documentation and specify your style guidelines for immediate polishing.

Frequently Asked Questions about copyedit-docs

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

FAQPage Schema
How do I enforce active voice and consistency in technical documentation?

To enforce active voice and consistency in technical documentation, paste your draft content and specify your style guidelines to automatically polish text into publish-ready material with correct punctuation and standardized terminology.

What is the best way to polish API references and release notes for readability?

Polishing API references and release notes for readability involves optimizing sentence length, enforcing active phrasing, and checking terminology consistency across multiple documents to meet your specific style guidelines.

Can I standardize terminology across large technical manuals for multiple teams?

Yes, you can standardize terminology across large technical manuals by applying consistency checks that scale from single-page documents to comprehensive guides, ensuring uniform style and formatting across distributed teams.

How do I prevent smothered verbs and fix punctuation in developer guides?

To prevent smothered verbs and fix punctuation in developer guides, apply automated copyediting that enforces concise phrasing, punctuation hygiene, and sentence-case headings throughout the text.

Do I need a style guide to copyedit product docs?

Specifying your style guidelines is required to copyedit product docs effectively, as the Skill uses them to enforce active voice, standardize terminology, and ensure the final output meets your team's formatting rules.