writing-natural

Write human-readable prose using rules from the Elements of Style.

1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/stefanfaur/roach-marketplace --skill writing-natural-stefanfaur
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-natural
Source: https://github.com/stefanfaur/roach-marketplace/tree/main/roach/skills/writing-natural
Command: npx skills add https://github.com/stefanfaur/roach-marketplace --skill writing-natural-stefanfaur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated prose often reads as vague, passive, and padded. This Skill enforces classic style rules so documentation, READMEs, changelogs, and other human-facing text come out direct, concrete, and readable. ## Core Features & Use Cases - Style Rule Enforcement: Applies six rules from the Elements of Style — active voice, positive form, concrete language, omitted needless words, related words kept together, and emphatic words placed at the end. - Mandatory Style Guide Reading: Requires reading the full elements-of-style.md reference before writing anything, grounding output in the source text. - Use Case: When drafting a project README or changelog entry, the Skill produces prose with a natural voice and strong sentence endings instead of generic AI phrasing. ## Quick Start Ask the assistant to write or rewrite a README section using the writing-natural skill so it follows the Elements of Style rules.

Frequently Asked Questions about writing-natural

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

FAQPage Schema
How do I make AI-written documentation sound more natural?▼

Apply the Elements of Style rules: use active voice, positive statements, concrete language, and omit needless words. This Skill reads the full style guide first, then writes prose following those rules for any human-facing text.

What is the difference between writing-natural and writing-simply?▼

writing-natural uses the Elements of Style and keeps a natural voice with emphatic sentence endings. writing-simply uses ASD-STE100 Simplified Technical English, strips voice for plainness, and includes a linter. Pick one per document since they conflict sentence by sentence.

When should I use Simplified Technical English instead of the Elements of Style?▼

Use writing-simply when text must be plain, uniform, and machine-checkable, or when the user asks for plain language or AI slop removed. Use writing-natural when the prose should retain a voice and rhetorical emphasis.

Which Elements of Style rules does this Skill apply?▼

It applies six rules: Rule 10 (active voice), Rule 11 (positive form), Rule 12 (definite, specific, concrete language), Rule 13 (omit needless words), Rule 16 (keep related words together), and Rule 18 (emphatic words at the end).

What types of content can this Skill write?▼

It covers any prose read by humans: documentation, READMEs, changelogs, summaries, skill content, and command content. It has no modes, subagents, or file organization — it reads the style guide and writes.