write-prose

Standardize English prose using Strunk and White and Zinsser style rules.

5|3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/leifericf/agentic-sdk --skill write-prose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-prose
Source: https://github.com/leifericf/agentic-sdk/tree/main/skills/write-prose
Command: npx skills add https://github.com/leifericf/agentic-sdk --skill write-prose

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation of professional English prose by ensuring clarity, brevity, and adherence to style conventions, eliminating common issues such as overuse of words, unneeded embellishments, and AI-generated jargon.

Core Features & Use Cases

  • Prose Standardization: Enforces the use of a standard writing style that is concise and humanized.
  • Style Consistency: Ensures all written content adheres to a set of eight fundamental style rules, with references to the Strunk and White's Elements of Style and Zinsser's On Writing Well.
  • Use Case: If you're working on a project and need to write documentation, commit messages, or comments that convey complex information in an easily understandable way, use this Skill to enhance your prose.

Quick Start

Before writing prose in your project, refer to the Skill 'write-prose' to maintain style consistency and adherence to the project's standards.

Frequently Asked Questions about write-prose

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

FAQPage Schema
How do I standardize technical writing style for project documentation?

Standardize technical writing style by applying eight fundamental rules derived from Strunk and White, and Zinsser, ensuring your project documentation remains concise, humanized, and free of AI-generated jargon.

What is the best way to write clear commit messages and code comments?

Writing clear commit messages and code comments requires enforcing brevity and removing unneeded embellishments, which this prose optimization approach achieves by strictly adhering to established style conventions.

How do I remove AI-generated jargon from technical design docs?

Remove AI-generated jargon from technical design docs by applying a standardization process that bans AI tells and enforces humanized language based on classic style guides like Elements of Style.

Can I use this prose standardization for Architecture Decision Records?

Yes, you can use this prose standardization for Architecture Decision Records because it streamlines the creation of professional English prose across all project artifacts, ensuring clarity and style consistency.

Why does my technical documentation contain overproduced text?

Technical documentation often contains overproduced text due to unneeded embellishments and overuse of words, which this prose standardization process reduces by applying strict style conventions from On Writing Well.

Do I need specific dependencies to enforce prose style conventions?

No specific dependencies are required to enforce prose style conventions; the standardization operates independently to apply its eight fundamental rules directly to your project's text outputs.