orwell-writing
Use when an agent is asked to draft, rewrite, edit, review, polish, copyedit, simplify, humanize, or create written prose, including creative writing, essays…
Skill by Tam Nguyen
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/amahony-orwell-writing
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: writing, agent-building
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/orwell-writing
What's inside
- Skill name
orwell-writing- Description
- Use when an agent is asked to draft, rewrite, edit, review, polish, copyedit, simplify, humanize, or create written prose, including creative writing, essays, posts, scripts, speeches, emails, documentation, product copy, and other style-sensitive text. Apply George Orwell's six rules and ASD-STE100 Simplified Technical English as a plain-English discipline while preserving the user's intended meaning, audience, tone, and explicit constraints.
- License
- MIT
- Metadata
- author: Tam Nguyen · source: https://github.com/tamdogood/builder-essential-skills/tree/main/skills/orwell-writing · version: 1.0.0 · category: Writing
- Instructions
- 62 lines in SKILL.md · view on GitHub
Files (2)
- LICENSE
- SKILL.md
SKILL.md (first lines)
# Orwell Writing ## Overview Use Orwell's rules and ASD-STE100 Simplified Technical English (STE) as practical filters for clear, direct, and honest prose. Use STE by default for technical, instructional, business, and product prose. Apply the rules to both drafting and revision, but do not erase deliberate voice, character, rhythm, humor, or genre when the user clearly wants them. STE has writing rules and a controlled dictionary. Use an approved word with its approved meaning when the dictionary is available. Do not claim strict STE conformance without checking the current ASD-STE100 issue and dictionary. ## Core Rules Remember these rules from "Politics and the English Language": 1. Never use a metaphor, simile, or other figure of speech which you are used to seeing in print. 2. Never use a long word where a short one will do. 3. If it is possible to cut a word out, always cut it out. 4. Never use the passive where you can use the active. 5. Never use a foreign phrase, a scientific word, or a jargon word if you can think of an everyday English equivalent. 6. Break any of these rules sooner than say anything outright barbarous. ## ASD-STE100 baseline For technical and instructional prose: 1. Use short sentences. Put one main action or statement in each sentence. 2. Use a clear subject and an active verb. Name the actor when the actor matters. 3. Use the same term for the same thing. Do not change a term only to avoid repetition. 4. Use familiar words with one precise meaning. Avoid idioms, slang, figurative language, and vague verbs. 5. Use a specific technical term when it is necessary for accuracy. Define it or link to its definition. 6. Keep noun groups short. Use prepositions to show relationships between terms. 7. Write procedures as direct instructions. State the condition, action, and expected result. 8. Use positive instructions when they are clear. State what the reader must do. 9. Use one spelling variety consistently: the organisation's style guide if there is one, otherwise British English. 10. Preserve code, commands, identifiers, product names, legal text, and required quotations. Do not simplify them silently. When strict STE is not possible, keep the text clear and mark the terms or passages that need a domain-specific exception. ## Workflow When writing from scratch: 1. Identify the audience, purpose, and promised tone from the user's request. 2. Draft in concrete, direct English. 3. Remove stock phrases, dead metaphors, filler, pompous diction, needless abstraction, and avoidable jargon. 4. Prefer active verbs and clear subjects unless passive voice better serves emphasis, tact, suspense, or technical accuracy. 5. Keep necessary nuance; do not make prose crude, false, or flat just to make it short. 6. Apply the ASD-STE100 baseline. Check terms, sentence structure, instructions, and technical exceptions. When revising existing text: 1. Preserve the user's meaning and any explicit tone or format constraints. 2. Cut words, clauses, and sentences that do no work. 3. Replace stale figures of speech with plain phrasing or a fresh, specific image. 4. Replace long, foreign, scientific, or jargon terms with everyday English when accuracy permits. 5. Convert passive constructions to active ones when the actor matters and is known. 6. Flag any remaining jargon, passive voice, or ornate phrasing that is necessary rather than silently removing important precision. 7. Run a final STE pass. Check that each technical term is consistent, each instruction states the required action, and each exception is intentional. ## Creative Writing For fiction, poetry, memoir, scripts, and lyrical prose, treat STE as a clarity aid, not a requirement that overrides the user's form. Keep intentional ambiguity, cadence, dialogue style, imagery, and character voice when they create a real effect. Remove only language that feels inherited, inflated, evasive, or lazy. Use strict STE when the user explicitly requests it, and note when that request conflicts with a creative effect.
From amahony/agent-templates, MIT.
More from amahony/agent-templates
- 0.570score
phase-planning
Jeremy Kaye
Create and maintain phase files, the plans that break work into phases, sprints and tasks with a status for every task.
SkillAFreshness: AClaude Code +9 - 0.570score
blog-post-writing
Tam Nguyen
Write a blog post that reads like a person wrote it and earns search traffic.
SkillAFreshness: AClaude Code +9 - 0.570score
business-naming
Tam Nguyen
Generate, refine, compare and, when needed, screen distinctive names for startups, products, apps, developer tools, open-source projects, product families…
SkillAFreshness: AClaude Code +9 - 0.570score
design-system-planning
Jeremy Kaye
Set a product's visual design language and screen contracts after the product plan and before phase planning.
SkillAFreshness: AClaude Code +9 - 0.570score
mastery-plan
Tam Nguyen
Build an evidence-based path toward exceptional capability in a field or skill, and coach the learner along it.
SkillAFreshness: AClaude Code +9 - 0.570score
paper-opportunity-radar
Tam Nguyen
Run a cumulative daily or one-off sweep of research papers on a chosen topic, audit their claims, methods, integrity signals and independent support, then…
SkillAFreshness: AClaude Code +9 - 0.565score
customer-reply
Omni
Draft replies to customer emails and support messages in the company voice.
SkillAFreshness: AClaude Code +9 - 0.565score
decision-record
Omni
Write a decision record capturing context, options considered, and the chosen option.
SkillAFreshness: AClaude Code +9 - 0.565score
deep-explanation
Tam Nguyen
Explain any topic from first principles as a layered, causal explanation that fully answers the question.
SkillAFreshness: AClaude Code +9 - 0.565score
onboarding-guide
Omni
Walk a new team member through how the team works, one step at a time, using the onboarding checklist in this skill.
SkillAFreshness: AClaude Code +9 - 0.565score
document-review
Omni
Review a draft document for clarity, structure, tone, and errors, and return prioritised feedback.
SkillAFreshness: AClaude Code +9 - 0.565score
job-description
Omni
Write a job description in house format from a hiring manager's notes.
SkillAFreshness: AClaude Code +9
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Oct 19, 2026 (9 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- Version
- 1.0.0
- License
- MIT
- Repository
- github.com/amahony/agent-templates
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from Tam Nguyen
- 0.570score
paper-opportunity-radar
Tam Nguyen
Run a cumulative daily or one-off sweep of research papers on a chosen topic, audit their claims, methods, integrity signals and independent support, then…
SkillAFreshness: AClaude Code +9 - 0.570score
blog-post-writing
Tam Nguyen
Write a blog post that reads like a person wrote it and earns search traffic.
SkillAFreshness: AClaude Code +9 - 0.570score
business-naming
Tam Nguyen
Generate, refine, compare and, when needed, screen distinctive names for startups, products, apps, developer tools, open-source projects, product families…
SkillAFreshness: AClaude Code +9 - 0.570score
mastery-plan
Tam Nguyen
Build an evidence-based path toward exceptional capability in a field or skill, and coach the learner along it.
SkillAFreshness: AClaude Code +9 - 0.565score
deep-explanation
Tam Nguyen
Explain any topic from first principles as a layered, causal explanation that fully answers the question.
SkillAFreshness: AClaude Code +9 - 0.565score
market-validation
Tam Nguyen
Run an honest market-fit and viability audit of a project or idea and produce a decision document.
SkillAFreshness: AClaude Code +9
Cite this page
orwell-writing skill. Agent Mart. https://agentmart.dev/skills/amahony-orwell-writing (last updated 2026-10-24)