skills/writing-general/SKILL.md
Internal skill for Strunk & White writing rules. Loaded by /writing for quick edits or as base layer for domain skills.
npx skillsauth add edwinhu/workflows writing-generalInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Foundational style guide for clear, concise prose based on Strunk & White's Elements of Style.
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.
| 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 |
| Thought | Why It's Wrong | Do Instead | |---------|----------------|------------| | "I'll add some qualifiers to be safe" | Weakens the writing | Make definite assertions | | "Let me list these points" | Bullet points are lazy | Write in prose paragraphs | | "I should sound more formal" | Formality often means wordiness | Write naturally, then edit | | "This needs more emphasis" | Overemphasis dilutes meaning | Let strong words speak |
| Excuse | Reality | Do Instead | |--------|---------|------------| | "The passive voice is fine here" | Passive voice hides the actor; name them | REWRITE in active voice | | "This adverb adds emphasis" | Strong verbs don't need adverbs | DELETE the adverb, pick a stronger verb | | "The reader needs this context first" | Lead with the point, add context after | MOVE the point to the front | | "This paragraph needs one more sentence" | If the paragraph is complete, stop | STOP writing and move on | | "I should vary the sentence structure" | Clarity beats variety; don't complexify for style | KEEP the clear structure |
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.
Skipping the sentence-level check is NOT HELPFUL — the user publishes weak prose that undermines their credibility. Reading your own output and thinking "looks good" is not editing.
| 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 |
For comprehensive guidance, consult:
references/elements-of-style.md - Complete Strunk & White guide covering:
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.
After completing any writing task, invoke /ai-anti-patterns to check for AI writing indicators.
testing
Internal skill for literature review and source materialization. Called after brainstorm, before setup. NOT user-facing.
documentation
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.
testing
Validate draft sections cover all PRECIS claims before review.
testing
Internal skill for creating PRECIS.md, OUTLINE.md, and ACTIVE_WORKFLOW.md. Called after brainstorm sources are gathered.