pelizzai-writing-clearly-and-concisely

Apply Strunk Jr.'s writing principles to remove superfluous words from technical prose.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/rpelizza/PelizzAI --skill pelizzai-writing-clearly-and-concisely
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pelizzai-writing-clearly-and-concisely
Source: https://github.com/rpelizza/PelizzAI/tree/main/.agents/skills/pelizzai-writing-clearly-and-concisely
Command: npx skills add https://github.com/rpelizza/PelizzAI --skill pelizzai-writing-clearly-and-concisely

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the tendency of AI to produce generic, inflated, and repetitive prose, helping you write with the clarity, force, and precision of human-authored professional writing.

Core Features & Use Cases

  • Style Enforcement: Applies William Strunk Jr.'s timeless rules of grammar, punctuation, and composition to your drafts.
  • AI Pattern Detection: Identifies and removes common AI-generated crutch words, inflated adjectives, and empty phrases.
  • Use Case: Use this skill to refine technical documentation, pull request descriptions, or important emails to ensure they are concise, active, and human-readable.

Quick Start

Load the elementary principles of composition section and apply its rules to rewrite the provided draft for maximum clarity and impact.

Frequently Asked Questions about pelizzai-writing-clearly-and-concisely

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

FAQPage Schema
How do I eliminate AI-typical patterns and inflated vocabulary from technical documentation?

To eliminate AI-typical patterns from technical documentation, apply William Strunk Jr.'s composition rules to remove superfluous words, crutch vocabulary, and empty phrases. This process enforces active voice usage and precise grammar, resulting in concise, human-readable professional prose.

What is the best way to write concise commit messages and pull request descriptions?

The best way to write concise commit messages and pull request descriptions is to apply elementary composition principles that target and remove generic, repetitive prose. This approach enforces vigorous style, active voice, and established grammar rules to maximize clarity and impact for human readers.

How do I apply Strunk's principles to improve clarity and concision in professional communication?

Apply Strunk's principles to improve clarity and concision by loading established grammar and composition rules, then using them to rewrite drafts. This identifies and removes superfluous words and inflated adjectives, ensuring your professional communication adheres to established rules while maintaining force and precision.

Does this writing style enforcement work for general emails and professional communication?

Yes, this writing style enforcement works for general emails and professional communication. It targets documentation, commit messages, and general communication to identify and remove common AI-generated crutch words, ensuring your important emails are concise, active, and human-readable.

Why does AI-generated prose sound generic and how can I fix it?

AI-generated prose sounds generic due to a tendency to produce inflated, repetitive text with crutch words and empty phrases. You can fix it by applying William Strunk Jr.'s timeless rules of grammar and composition to refine your drafts, ensuring the output has the force and precision of human-authored writing.

When should I not use established grammar rules to rewrite technical drafts?

You should not use established grammar rules to rewrite technical drafts when your text requires specific formatting, localized syntax, or specialized vocabulary that intentionally deviates from standard composition rules. This approach strictly enforces active voice and eliminates inflated terminology for general professional contexts.