writing-general
Internal skill for Strunk & White writing rules. Loaded by /writing for quick edits or as base layer for domain skills.
Best use case
writing-general is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Internal skill for Strunk & White writing rules. Loaded by /writing for quick edits or as base layer for domain skills.
Teams using writing-general should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/writing-general/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How writing-general Compares
| Feature / Agent | writing-general | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Internal skill for Strunk & White writing rules. Loaded by /writing for quick edits or as base layer for domain skills.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# General Writing Rules (Strunk & White)
Foundational style guide for clear, concise prose based on Strunk & White's Elements of Style.
## Core Principles
### The Iron Law of Good Writing
**Omit needless words.**
Every word must earn its place. Vigorous writing is concise. A sentence should contain no unnecessary words, a paragraph no unnecessary sentences.
### Critical Rules
| Rule | Explanation |
|------|-------------|
| Write in prose | Avoid bullet points and lists unless explicitly requested |
| Use active voice | "The committee approved the plan" not "The plan was approved" |
| Be concrete | Specific details over vague abstractions |
| Put statements in positive form | Say what something is, not what it isn't |
| Use definite language | Avoid hedging, qualifiers, and weasel words |
### Red Flags
- About to add qualifiers "to be safe" → STOP. Hedging weakens the writing; make definite assertions.
- About to reformat prose into bullet points → STOP. Write prose paragraphs unless lists were explicitly requested.
- About to formalize the register → STOP. Formality usually means wordiness; write naturally, then edit.
- About to add emphasis → STOP. Overemphasis dilutes meaning; let strong words speak.
### Delete & Restart Triggers
**If you catch yourself writing ANY of these, DELETE THE SENTENCE and START FRESH:**
| Anti-Pattern | Restart Approach |
|---|---|
| "It is [adjective] that..." | Rewrite as direct assertion |
| "There are [X] reasons" | Replace with direct list or synthesis |
| "In order to" | Replace with "to" |
| Sentence > 40 words with nested clauses | Break into 2-3 sentences |
| Passive voice hiding the actor | Name the actor, use active voice |
After deleting, restart the sentence with THE POINT first, then evidence.
**Skipping the deletion pass is NOT HELPFUL — the user publishes bloated prose that buries their argument.** Identify violations and purge them.
## Editing Checklist
### Sentence Level
- Remove unnecessary words ("in order to" → "to")
- Replace weak verbs ("is able to" → "can")
- Convert passive to active voice
- Eliminate redundancies ("past history" → "history")
### Paragraph Level
- Ensure each paragraph has one main idea
- Check topic sentences lead clearly
- Verify logical flow between paragraphs
### Word Level
- Replace abstract nouns with concrete ones
- Use specific verbs over vague ones + adverbs
- Cut filler words ("very", "really", "quite", "rather")
## Quick Reference: Common Fixes
| Weak | Strong |
|------|--------|
| utilize | use |
| in order to | to |
| due to the fact that | because |
| at this point in time | now |
| in the event that | if |
| prior to | before |
| subsequent to | after |
| with regard to | about |
| a large number of | many |
| is able to | can |
## Progressive Disclosure
For comprehensive guidance, consult:
- **`references/elements-of-style.md`** - Complete Strunk & White guide covering:
- Elementary Rules of Usage (commas, colons, participles)
- Elementary Principles of Composition (paragraph unity, active voice)
- Words and Expressions Commonly Misused
- Style guidance and literary reminders
## Examples
**Weak original:**
> It is important to note that there are a variety of different factors that contribute to the overall success of the project in question.
**Strong revision:**
> Several factors determine project success.
**Weak original:**
> The report was written by the team and was subsequently reviewed by management prior to being distributed to stakeholders.
**Strong revision:**
> The team wrote the report, management reviewed it, and stakeholders received it.
## Integration
After completing any writing task, invoke `/ai-anti-patterns` to check for AI writing indicators.Related Skills
writing
This skill should be used when the user asks to 'write a paper', 'start a writing project', 'draft an article', 'write about', 'brainstorm writing topics', 'gather sources for a paper', 'what should I write about', or needs the writing workflow entry point for any writing task.
writing-validate
Validate draft sections cover all PRECIS claims before review.
writing-setup
Internal skill for creating PRECIS.md, OUTLINE.md, and ACTIVE_WORKFLOW.md. Called after brainstorm sources are gathered.
writing-revise
This skill should be used when the user asks to 'revise writing', 'fix review issues', 'polish draft', 'apply review feedback', 'complete writing workflow', or after /writing-review produces REVIEW.md with issues to fix.
writing-review
Internal skill for hierarchical document review. Called by writing-validate after claim validation passes.
writing-precis-reviewer
Internal skill used by writing-setup at exit gate. Dispatches a reviewer subagent to verify PRECIS.md quality before outlining. NOT user-facing.
writing-outline
Internal skill for creating detailed section outlines. Called by /writing workflow after PRECIS and master OUTLINE are complete.
writing-outline-reviewer
Internal skill used by writing-outline at exit gate. Dispatches a reviewer subagent to verify OUTLINE.md quality before drafting. NOT user-facing.
writing-lit-review
Internal skill for literature review and source materialization. Called after brainstorm, before setup. NOT user-facing.
writing-legal
Internal skill for academic legal writing. Loaded by /writing when style=legal. Based on Volokh's "Academic Legal Writing".
writing-handoff
Create structured handoff document for writing workflow session pause/resume.
writing-econ
Internal skill for economics and finance writing. Loaded by /writing when style=econ. Based on McCloskey's "Economical Writing".