Install
$ agentstack add skill-tamdogood-builder-essential-skills-orwell-writing ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Orwell Writing
Overview
Use Orwell's rules as a practical filter for clarity, force, and honesty in English prose. Apply them to both drafting and revision, but do not erase deliberate voice, character, rhythm, humor, or genre when the user clearly wants them.
Core Rules
Remember these rules from "Politics and the English Language":
- Never use a metaphor, simile, or other figure of speech which you are used to seeing in print.
- Never use a long word where a short one will do.
- If it is possible to cut a word out, always cut it out.
- Never use the passive where you can use the active.
- Never use a foreign phrase, a scientific word, or a jargon word if you can think of an everyday English equivalent.
- Break any of these rules sooner than say anything outright barbarous.
Workflow
When writing from scratch:
- Identify the audience, purpose, and promised tone from the user's request.
- Draft in concrete, direct English.
- Remove stock phrases, dead metaphors, filler, pompous diction, needless abstraction, and avoidable jargon.
- Prefer active verbs and clear subjects unless passive voice better serves emphasis, tact, suspense, or technical accuracy.
- Keep necessary nuance; do not make prose crude, false, or flat just to make it short.
When revising existing text:
- Preserve the user's meaning and any explicit tone or format constraints.
- Cut words, clauses, and sentences that do no work.
- Replace stale figures of speech with plain phrasing or a fresh, specific image.
- Replace long, foreign, scientific, or jargon terms with everyday English when accuracy permits.
- Convert passive constructions to active ones when the actor matters and is known.
- Flag any remaining jargon, passive voice, or ornate phrasing that is necessary rather than silently removing important precision.
Creative Writing
For fiction, poetry, memoir, scripts, and lyrical prose, treat the rules as pressure, not law. Keep intentional ambiguity, cadence, dialogue style, image, and character voice when they create a real effect. Remove only the language that feels inherited, inflated, evasive, or lazy.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: tamdogood
- Source: tamdogood/builder-essential-skills
- License: MIT
- Homepage: https://www.npmjs.com/package/@tamng0905/builder-essential-skills
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.