writing-clearly-and-concisely

Apply Strunk's composition principles to clarify technical and professional prose.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/chokky-education/science-club-web --skill writing-clearly-and-concisely-chokky-education
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-clearly-and-concisely
Source: https://github.com/chokky-education/science-club-web/tree/main/.agents/skills/writing-clearly-and-concisely
Command: npx skills add https://github.com/chokky-education/science-club-web --skill writing-clearly-and-concisely-chokky-education

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the tendency of LLMs to produce generic, puffy, and overly formal language, ensuring your writing is direct, professional, and human-centric.

Core Features & Use Cases

  • Strunk's Principles: Applies timeless rules like active voice, positive form, and concrete language to improve clarity.
  • AI Pattern Detection: Identifies and removes common LLM filler words, promotional adjectives, and empty phrases.
  • Use Case: Use this skill to refine technical documentation, polish pull request descriptions, or simplify complex error messages for better user comprehension.

Quick Start

Use the writing-clearly-and-concisely skill to review my draft for passive voice and remove any generic AI-generated filler words.

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 AI filler words and puffery from technical documentation?

Remove AI filler words from technical documentation by applying Strunk's principles of composition, which detect and eliminate promotional adjectives, hedging, and generic LLM-generated puffery to ensure direct, professional prose.

What is the best way to eliminate passive voice in commit messages?

Eliminate passive voice in commit messages by applying active voice and positive form rules derived from Strunk's elements of style, transforming vague statements into concrete, professional language.

How do I simplify complex error messages for better user comprehension?

Simplify complex error messages by applying stylistic guidance that removes hedging and empty phrases, replacing them with clear, human-centric language that improves user comprehension.

Does this approach work for refining pull request descriptions?

Yes, this approach effectively refines pull request descriptions by identifying and removing common LLM filler words and passive voice, ensuring the text is direct and professional.

Why does LLM-generated writing sound overly formal and generic?

LLM-generated writing sounds overly formal and generic because it relies on empty phrases, promotional adjectives, and hedging, which can be corrected by applying timeless composition rules like active voice and concrete language.

When do I need to apply Strunk's principles to professional prose?

Apply Strunk's principles to professional prose when technical documentation, commit messages, or user-facing text requires refinement to eliminate passive voice, hedging, and generic AI-generated filler words.