elements-of-style
Skill1 starsChanged 3 months agoMITView on GitHub
Mechanical and compositional edit pass from William Strunk Jr.'s 1920 Elements of Style — usage, punctuation, active/positive/concrete prose, omit needless words, parallel construction. Use when tightening sentences, fixing comma splices, dangling modifiers, vague diction, or when the user cites Strunk, Elements of Style, or asks for a usage/concision pass. Prefer writing-prose for anti-slop / human tone; style-clarity-grace for turgid syntax; writer-style for a named voice; writing-technical for form; writing-docs for procedures. Prefer the writing hub when the writing path is unclear.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- jcsaaddupuy/badrobotstheir own version, first seen Feb 26, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- jcsaaddupuy/badrobots★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository47 other files it gives its agents.
- data-apache-lakehouseSkill
- data-apiSkill
- dataSkill
- data-duckdbSkill
- data-identity-resolutionSkill
- data-pipeline-operationsSkill
- data-pokemon-tcg-foundationsSkill
- data-product-evalSkill
- data-reelsSkill
- data-semantic-qualitySkill
- data-table-lifecycleSkill
- html-designSkill
- ebay-listingSkill
- flutter-pro-ux-reviewSkill
- flutterSkill
- browser-testing-with-devtoolsSkill
- browser-verifySkill
- design-systemSkill
- frontend-designSkill
- mobile-app-echarts-visualSkill
- mobile-blog-chart-visualSkill
- mobile-chart-visualSkill
- mobile-product-uxSkill
- mockup-implementSkill
- product-designSkill
- product-ui-craftSkill
- prototypeSkill
- react-performanceSkill
- ui-exploreSkill
- visual-verifySkill
- web-qualitySkill
- high-retention-insight-reels-instagramSkill
- instagramSkill
- instagram-virality-insightsSkill
- marketing-cashvertisingSkill
- marketing-contagiousSkill
- marketing-going-viralSkill
- marketingSkill
- marketing-offersSkill
- marketing-storybrandSkill
- quality-checkSkill
- style-clarity-graceSkill
- writer-styleSkill
- writing-docsSkill
- writing-proseSkill
- writingSkill
- writing-technicalSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 53
Every word should tell. Prefer the specific to the general, the definite to the vague, the concrete to the abstract.
- Distinctive: line 69
Do not restyle first. Scan, then fix.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Elements of Style — usage + composition pass
Job: Make the sentences correct, concrete, and tight. Do not restyle voice.
Source: William Strunk Jr., The Elements of Style (Harcourt, 1920). Public domain. This skill distills the 1920 rules into an agent checklist. It is not the 4th edition (Strunk & White, 1999/2000, still copyrighted).
Full 1920 text: references/strunk-1920.md
Usage detail: references/usage.md
Composition detail: references/composition.md
Padding words: references/misused-words.md
When to load
- Edit pass after a draft exists (hub pipeline D)
- “Tighten this,” “Strunk this,” “fix the grammar,” “omit needless words”
- Comma splices, dangling modifiers, mushy abstracts, padded the fact that
Not for: inventing a voice, picking a blog mode, writing a runbook from scratch, or landing-page conversion.
Do not fight the other writing skills
| Keep | Do not “Strunk away” |
Intentional short punches (writing-prose) | Accidental fragments that read like errors |
| Passive when the receiver is the topic | Dummy there is / it was |
| Human seams, specifics, mixed feeling | Padding that pretends to be a seam |
| Frozen facts / numbers | Rewrites that change a claim |
Strunk himself: break a rule only when the sentence gains a compensating merit.
Skip as hard fails (dated or house-overridden): shall/will person rules, split-infinitive ban, data must be plural, can vs may in informal prose.
Core rule
Every word should tell. Prefer the specific to the general, the definite to the vague, the concrete to the abstract. Put the actor in the subject and the action in the verb. Put the stress at the end.
Edit workflow
Copy and track:
Elements pass:
- [ ] Usage (1–7)
- [ ] Composition (8–18)
- [ ] Padding words
- [ ] Facts unchanged- Do not restyle first. Scan, then fix.
- Usage — possessives, series comma, paired parenthetic commas, comma before a coordinating conjunction, no comma splice (semicolon or period), no accidental fragment, opener participle refers to the subject.
- Composition — one topic per paragraph; active when the actor matters; positive form; concrete nouns; cut needless words; break and/but/so sing-song; parallel lists; keep related words together; one tense in a summary; emphatic words last.
- Padding — cut the fact that, case/factor/feature/nature/character, one of the most, interesting, along these lines, very, worth while.
- Return the edited text. List material changes in one short bullet list.
Fast checks (most drafts fail these)
- Needless words — the question as to whether → whether; owing to the fact that → since; he is a man who → he; in a hasty manner → hastily.
- Dummy subjects — There were dead leaves on the ground → Dead leaves covered the ground.
- Not-evasion — he was not often on time → he usually came late.
- Dangler — On arriving in Chicago, his friends met him → When he arrived…
- Comma splice — two complete clauses need a semicolon, a period, or and/but/for plus a comma.
- Parallelism — to swim, to bike, and running → to swim, to bike, and to run.
- Related words — don’t split a verb from its object with a long aside.
Hand off
| Need | Skill |
| Turgid / nominalized / no actor | style-clarity-grace |
| Human tone / anti-slop, no persona | writing-prose |
| Named voice (default: Evan) | writer-style |
| Research / build-log form | writing-technical |
| Runbook / API reference | writing-docs |
| Offer / landing | marketing |
| Unclear writing path | writing hub |
Done criteria
- Usage errors that change meaning or look like mistakes are gone
- Actors in subjects, actions in verbs, except when topic requires passive
- Concrete where the draft was abstract
- Needless words cut; facts and numbers untouched
- Intentional fragments and voice seams still stand
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

