writing-clearly-and-concisely

Rewrites prose using Strunk's style rules while removing common AI writing patterns.

Updated May 27, 2026
One-click install
npx skills add https://github.com/baljinnyamday/autonomous-red-team-agent --skill writing-clearly-and-concisely-baljinnyamday
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-clearly-and-concisely
Source: https://github.com/baljinnyamday/autonomous-red-team-agent/tree/main/paper/.agents/skills/writing-clearly-and-concisely
Command: npx skills add https://github.com/baljinnyamday/autonomous-red-team-agent --skill writing-clearly-and-concisely-baljinnyamday

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Prose written or edited by LLMs tends to be wordy, passive, and padded with generic phrases like "pivotal", "seamless", and "delve". This Skill applies William Strunk Jr.'s The Elements of Style rules plus a field guide of AI writing patterns to produce clearer, more direct text for human readers. ## Core Features & Use Cases - Strunk's Core Rules: Enforces active voice, positive statements, concrete language, and omission of needless words across documentation, commit messages, error messages, and UI copy. - AI Pattern Detection: Flags puffery, empty "-ing" phrases, promotional adjectives, and overused AI vocabulary using Wikipedia's field guide to AI-generated content. - Progressive Reference Loading: Loads only the needed section file (grammar, composition, formatting, or word choice) to conserve context, with subagent support for tight-context editing. - Use Case: Paste a draft README or commit message and ask for a clarity pass; the Skill rewrites it in active voice, cuts filler, and removes AI-sounding language. ## Quick Start Ask the assistant to edit your draft documentation or commit message for clarity using Strunk's composition principles and AI-pattern avoidance.

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 make AI-generated writing sound less generic?

Remove puffery words like pivotal, crucial, and seamless, cut empty "-ing" phrases such as "ensuring reliability", and replace vague claims with specific concrete statements. This Skill applies those edits using Wikipedia's field guide to AI writing patterns.

How to write clearer documentation and commit messages?

Apply Strunk's core rules: use active voice, put statements in positive form, use definite and concrete language, and omit needless words. The composition reference file covers these principles with before-and-after examples.

What are the most common signs of AI-generated text?

Common signs include overused vocabulary like delve, leverage, and tapestry, undue emphasis on importance and legacy, superficial "-ing" analyses, promotional tone, and formulaic conclusions. The signs-of-ai-writing reference catalogs these patterns with examples.

Does this Skill work when context window space is limited?

Yes. The SKILL.md core loads in about 1,000 tokens, and individual reference sections load on demand at 1,000-4,500 tokens each. For tight contexts, you can dispatch a subagent with your draft and one section file for copyediting.

When should I not use Strunk's style rules?

The rules target expository and technical prose for human readers. They are less suited to creative writing, dialogue, or contexts where deliberate stylistic choices override concision, and the passive voice remains valid when the subject requires it.