Qwriting-clearly

Refine prose for clarity and conciseness using Strunk's principles.

6|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/inho-team/qe-framework --skill qwriting-clearly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Qwriting-clearly
Source: https://github.com/inho-team/qe-framework/tree/main/skills/Qwriting-clearly
Command: npx skills add https://github.com/inho-team/qe-framework --skill qwriting-clearly

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Refines text for clarity and conciseness using Strunk's principles, and removes AI-generated writing patterns. It is suitable for documentation, commit messages, error messages, UI text, reports, and any writing that sounds robotic or overly formal.

## Core Features & Use Cases

  • Apply Strunk's rules to improve grammar, conciseness, and tone
  • Detect and remove AI-generated patterns to produce more human-like prose
  • Proofread and revise drafts, comments, README files, and UI copy
  • Use cases include documentation, code comments, PR descriptions, or error messages

Quick Start

Provide a draft paragraph and ask me to rewrite it for clarity using Strunk's principles.

Frequently Asked Questions about Qwriting-clearly

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

FAQPage Schema
How do I remove AI writing patterns from documentation and README files?

To remove AI writing patterns from documentation, provide a draft paragraph and prompt the rewrite for clarity. It applies Strunk's principles to detect robotic phrasing and suggests concrete language, avoiding inflated adjectives to produce human-like prose.

Can I use Strunk's principles to proofread technical explanations and UI text?

Yes, you can proofread technical explanations and UI text for conciseness by applying Strunk's rules for usage and composition. It refines drafts into clear, concise prose by suggesting concrete language and stripping overly formal or robotic sentence structures.

What is the best way to edit commit messages and error messages for clarity and conciseness?

The best way to edit commit messages and error messages is to apply Strunk's rules for conciseness. Input the draft text to revise inflated adjectives and robotic patterns, replacing them with direct, concrete language optimized for technical readers.

How do I refine reports and PR descriptions to sound less robotic and overly formal?

You can refine reports and PR descriptions by stripping AI-generated writing patterns and applying Strunk's composition rules. Input the draft to replace robotic structures with clear, concise, and human-like prose suitable for technical communication.

When should I not use automated prose polishing for code comments?

Avoid using automated prose polishing for code comments when preserving specific technical syntax or inline references is critical. The tool focuses on natural language conciseness and Strunk's grammar rules, which may alter standardized code documentation formats.

What is the best way to edit commit messages and error messages for clarity and conciseness?

The best way to edit commit messages and error messages is to apply Strunk's rules for conciseness. Input the draft text to revise inflated adjectives and robotic patterns, replacing them with direct, concrete language optimized for technical readers.