writing-clearly-and-concisely

Apply Strunk's composition rules to refine technical prose and remove AI patterns.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/imMamdouhaboammar/kaku-chatgpt-harness --skill writing-clearly-and-concisely-immamdouhaboammar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-clearly-and-concisely
Source: https://github.com/imMamdouhaboammar/kaku-chatgpt-harness/tree/main/.agents/skills/writing-clearly-and-concisely
Command: npx skills add https://github.com/imMamdouhaboammar/kaku-chatgpt-harness --skill writing-clearly-and-concisely-immamdouhaboammar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the tendency of AI to produce generic, puffy, and overly formal language, helping you transform drafts into clear, forceful, and human-centric prose.

Core Features & Use Cases

  • Strunk's Core Rules: Applies timeless composition principles like active voice, positive form, and omitting needless words.
  • AI Pattern Detection: Identifies and removes common LLM tropes such as empty -ing phrases, promotional adjectives, and grandiose vocabulary.
  • Use Case: Use this skill to refine technical documentation, polish commit messages, or simplify complex error messages to ensure they are direct and easy for humans to understand.

Quick Start

Load the writing-clearly-and-concisely skill and provide your draft text to receive a concise, professional revision.

Frequently Asked Questions about writing-clearly-and-concisely

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

FAQPage Schema
How do I remove generic AI patterns from technical documentation?

To remove generic AI patterns from technical documentation, this skill applies Strunk's principles to detect and eliminate empty phrases, promotional adjectives, and grandiose vocabulary, ensuring your prose is clear, forceful, and human-centric.

What is the best way to polish commit messages for professional communication?

The best way to polish commit messages is by applying timeless composition rules like active voice and omitting needless words, which refines technical drafts into concise, professional communication.

How does applying Strunk's principles improve technical communication?

Applying Strunk's principles improves technical communication by enforcing active voice, positive form, and omission of needless words, which transforms puffy AI-generated language into forceful, human-readable prose.

Can I use this to simplify complex error messages?

Yes, you can use this skill to simplify complex error messages by detecting generic LLM tropes and applying specific composition rules, ensuring your technical output is direct and easy for humans to understand.

When should I not use AI pattern detection for prose editing?

You should not use AI pattern detection for prose editing when your draft requires specialized formatting, complex narrative structures, or intentional stylistic formality that overrides standard clarity and conciseness rules.