Skip to main content
skill CX Codex

orwells-rules — Claude Code skill: editing and installation

This skill edits drafts using Orwell’s six writing rules, trimming clichés and excess words while favoring active voice. Use it to revise prose written by you or an agent.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add surendranb/writing-skills --skill orwells-rules -a claude-code
Open on GitHub

What orwells-rules does

orwells-rules guides an agent through a plain-language edit: replace worn-out figures of speech with direct wording, choose short words where they work, remove padding, and put the actor before the action. It also flags jargon. The rules are not absolute; clarity and natural phrasing take priority when a rigid edit would make a sentence awkward or incorrect.

The skill’s workflow starts by pinning down the intended thought, then moves through concrete imagery, cuts, active voice, and a final checklist. It requires a standard Markdown parser and agent context. Those are prerequisites, so an environment without them does not meet the stated requirements.

What it helps with

  • remove tired metaphors from a draft
  • swap long words for plain alternatives
  • rewrite passive sentences with named actors
  • cut padding and jargon from prose

Example prompts for the agent

  • Edit this draft using Orwell’s rules; remove clichés and unnecessary words.
  • Rewrite this paragraph in active voice and use plainer words.
  • Check this text against Orwell’s rules, keeping the phrasing natural.

How to install orwells-rules

1Skills CLI (Vercel)

npx skills add surendranb/writing-skills --skill orwells-rules -a claude-code

2Manually: put the files in place

~/.claude/skills/orwells-rules/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/orwells-rules/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about orwells-rules

How do I install orwells-rules in Claude Code?

Run npx skills add surendranb/writing-skills --skill orwells-rules -a claude-code. The skill file is at ~/.claude/skills/orwells-rules/SKILL.md.

What does orwells-rules do?

It guides an agent through Orwell’s six writing rules, including cutting clichés and padding, using everyday wording, and favoring active voice.

What does the skill need to work?

It requires a standard Markdown parser and agent context. Its rules also allow exceptions when following them would make the prose awkward or ungrammatical.

Source text

SKILL.md · MIT
---
name: orwells-rules
description: Apply George Orwell's 6 rules for clear, honest, and unpretentious writing from "Politics and the English Language" (1946). Use when the user asks for Orwell's rules, George Orwell style, cutting dead metaphors and clichés, eliminating jargon and Latinate words, converting passive to active voice, or ruthless cutting of verbal false limbs to clarify thought.
compatibility: Requires standard Markdown parser and agent context
---

# Orwell's Rules for Writing

Clarity over pretension, truth over ornament. Never let ready-made phrases think for you.

## The core rule

**Choose words for exact meaning and fresh imagery: cut stale metaphors, replace long Latinate words with short Saxon terms, strip every useless syllable, use active voice, and break any rule sooner than write barbarous prose.**

Workflow: `decide the exact thought` → `visualize concrete images` → `prune verbal false limbs and clichés` → `convert passive to active` → `run the Verify checklist`.

## Mechanics

1. **Ban dead metaphors.** Never use a metaphor, simile, or figure of speech you are used to seeing in print (e.g., *ring the changes*, *Achilles' heel*, *swan song*, *hotbed*, *stand shoulder to shoulder*, *toe the line*, *play into the hands of*, *no stone unturned*, *silver lining*). Use fresh, visual images or plain statements.
2. **Short Saxon words over long Latinates.** Never use a long word where a short one will do. Replace Latinate and polysyllabic terms with plain English (e.g., *help* not *facilitate*, *end* not *terminate*, *show* not *demonstrate*, *start* not *commence*, *try* not *endeavor*, *use* not *utilize*).
3. **Ruthless word-cutting (prune verbal false limbs).** If it is possible to cut a word out, always cut it out. Strip operator phrases that eliminate simple verbs (e.g., *render inoperative* → *break*, *make contact with* → *meet/call*, *give rise to* → *cause*, *have the effect of* → *do*, *in view of the fact that* → *because*).
4. **Active voice by default.** Never use the passive where you can use the active. Put the actor before the action ("The committee approved the budget" not "The budget was approved by the committee"). Eliminate bureaucratic evasions ("mistakes were made").
5. **Everyday English over foreign phrases and jargon.** Never use a foreign phrase, scientific word, or jargon if you can think of an everyday English equivalent (e.g., *status quo* → *current state*, *vis-à-vis* → *compared to*, *ad hoc* → *special/unplanned*, *synergy* → *cooperation*, *methodology* → *method*).
6. **The barbarism override (Rule 6).** Break any of these rules sooner than say anything outright barbarous. Clarity, honesty, and natural rhythm always override dogma.

## Verify

- Zero dead metaphors or prefabricated clichés from the ban list
- Long and Latinate words replaced with short Saxon equivalents
- Verbal false limbs pruned (no "render inoperative", "give rise to", "with regard to")
- Passive voice under 10% of total sentences; actors explicitly named
- Zero unneeded foreign phrases (*status quo*, *vis-à-vis*, *ad hoc*) or buzzwords
- Scrupulous writer self-check applied: (1) What am I trying to say? (2) What words express it? (3) Could I put it more shortly? (4) Is anything avoidably ugly?

## Do not

- Let ready-made phrases construct sentences or conceal your meaning
- Pad sentences with symmetrical extra syllables to sound authoritative
- Use vague euphemisms to sanitize unpleasant facts
- Enforce rules 1–5 so rigidly that prose becomes stiff, ungrammatical, or barbarous

## Example transformations

**Before:** "In view of the fact that the existing infrastructure has been rendered inoperative by recent events, it is considered imperative that proactive measures be commenced with a view to facilitating a prompt resolution."

**After:** "Because recent storms broke the power grid, we are fixing the lines today."

**Before:** "The committee must leave no stone unturned to explore every avenue vis-à-vis our competitive status quo, or we will play right into the hands of our rivals."

**After:** "The committee must check every option to improve our position before rivals beat us."

---

Source: George Orwell, "Politics and the English Language" (*Horizon*, April 1946).

© surendranb · MIT · surendranb/writing-skills

Similar skills

SKILL.md skills catalog →

From the same set16

shrek A writing skill that turns prose into the deadpan, grumpy, but warm voice of Shrek, grounding messages with swamp analogies. CX Codex +1 ★ 53repo stars scott-adams This skill helps trim prose, sharpen opening lines, and keep sentences short. Use it to revise writing with Scott Adams' business-writing method. CX Codex +1 ★ 53repo stars plain-language A skill that rewrites drafts in plain language: short sentences, active voice, no jargon. Useful for anything a reader sees once. CX Codex +1 ★ 53repo stars paddington Directs the assistant to write in the earnest and polite voice of Paddington. Useful for courteous customer replies and incident updates without blame. CX Codex +1 ★ 53repo stars journalism-ap A skill that holds the agent to Associated Press conventions when drafting news copy and press releases: attribution, numbers, dates, no editorializing. Useful when the text has to read as factual reporting. CX Codex +1 ★ 53repo stars jack-sparrow Rewrites plain announcements and updates into theatrical pirate prose inspired by Captain Jack Sparrow. Fits launch notes, status copy, and playful messages. CX Codex +1 ★ 53repo stars gov-uk-style This skill applies GOV.UK writing principles to public-facing content. Use it to revise help pages, service information, or policy summaries. CX Codex +1 ★ 53repo stars google-dev-docs A skill that makes the agent write technical docs the Google way: action headings, second person, present tense, active voice. Useful for READMEs, tutorials and API references. CX Codex +1 ★ 53repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor