clear-writing

Revise technical and user-facing prose for clarity, concision, and precision.

2|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/chriswch/praxis --skill clear-writing-chriswch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clear-writing
Source: https://github.com/chriswch/praxis/tree/main/skills/clear-writing
Command: npx skills add https://github.com/chriswch/praxis --skill clear-writing-chriswch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long, vague, or padded prose obscures meaning, wastes readers' time, and undermines technical communication. This Skill provides practical rules and examples to transform draft writing into direct, concrete, and readable prose so readers can quickly understand intent and act.

Core Features & Use Cases

  • Principled Revision: Guides edits for concision, active voice, positive statements, concrete language, parallel structure, and placing emphasis at sentence ends.
  • Machine-Habit Removal: Detects and removes common machine-generated padding, throat-clearing phrases, hedges, qualifiers, and filler constructions while preserving meaning.
  • Format-Specific Guidance: Tailors advice for documentation, specifications, design sketches, explanations, commit messages, and PR descriptions to match reader expectations and reviewer workflows.
  • Process Guidance: Recommends a two-step process: draft for completeness, then revise for clarity and structure.

Quick Start

Revise the following paragraph for clarity, concision, active voice, and concrete language while preserving technical accuracy.

Frequently Asked Questions about clear-writing

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

FAQPage Schema
How do I revise technical documentation for clarity and conciseness?

To revise technical documentation for clarity, apply active voice, concrete language, and parallel structure while removing padding and hedges. This preserves necessary detail and technical accuracy while ensuring readers grasp intent quickly.

What is the best way to remove filler and machine-generated padding from prose?

The best way to remove filler and machine-generated padding from prose is to detect and eliminate throat-clearing phrases, hedges, and qualifiers. This enforces positive phrasing and places emphasis at sentence ends while preserving the original meaning.

How do I write clear commit messages and PR descriptions?

Writing clear commit messages and PR descriptions requires tailoring prose to match reviewer workflows and reader expectations. Revise drafts to enforce active voice, concrete language, and concision so reviewers can quickly understand the intent and act.

Can I use a style guide to fix vague writing in design sketches and specifications?

Yes, you can use a style guide to fix vague writing in design sketches and specifications. Applying rules for active voice and positive statements transforms padded drafts into direct, readable prose while maintaining the necessary technical detail.

What is the recommended process for editing technical writing?

The recommended process for editing technical writing is a two-step approach: draft your content for completeness first, then revise the draft for clarity, structure, and concision to ensure readers can quickly understand the intent.

Why does my technical writing still seem vague after editing?

Technical writing often remains vague after editing when machine-habit padding, hedges, and qualifiers are left intact. You must enforce concrete language, remove filler constructions, and use parallel structure to make the prose direct and precise.