plain-language-copy-check
Skill1 starsChanged 16 days agoMITView on GitHub
Use this skill before any outreach or marketing copy goes out: a cold email, a LinkedIn DM, a follow-up, a post, a landing page section, a call script. Produces the copy rewritten to a 5th-grade reading level, with a pass/fail line for each check. Also use for "make this simpler", "too corporate", "plain English", "reading level", "sounds like a consultant", "would a busy founder get this". Not for sharpening a single headline or tagline.
In this repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- morning-paper-outreachSkill
- client-activation-checkinSkill
- client-churn-autopsySkill
- client-win-backSkill
- late-payment-chaseSkill
- network-path-mappingSkill
- rate-increase-planSkill
- sales-call-debriefSkill
- weekly-funnel-reviewSkill
- buyer-readSkill
- punch-upSkill
- call-topic-miningSkill
- ceo-exec-assistantSkill
- og-image-from-templateSkill
- weekly-site-and-ad-reportSkill
- icp-reviewSkill
- weekly-content-ideas-from-callsSkill
- client-performance-reviewSkill
- cold-email-sequenceSkill
- email-content-reviewerSkill
- scoring-analysis-and-distributionSkill
- delivery-audit-discovery-callSkill
- directionSkill
- rundownSkill
- source-checkSkill
- work-reviewSkill
- demandbird-exact-time-linkedin-postSkill
- kondo-owed-reply-sweepSkill
- linkedin-export-contact-importSkill
- mail-messages-contact-touchesSkill
- riverside-short-social-scheduleSkill
- youtube-transcript-panel-pullSkill
- email-voice-setupSkill
- upsell-opportunity-briefSkill
- ad-creative-content-strategySkill
- klaviyo-account-auditSkill
- facilitator-notesSkill
- local-prospectingSkill
- weekly-linkedin-postsSkill
- linkedin-watchlist-briefSkill
- pipeline-by-scriptSkill
- pre-session-flash-cardSkill
- write-in-the-owners-voiceSkill
- reddit-gtm-sprintSkill
- process-captureSkill
- sales-call-market-analyzerSkill
- linkedin-shoutout-postSkill
- revenue-goal-funnel-mathSkill
- case-study-buildSkill
- cash-runway-forecastSkill
- client-profitability-readSkill
- client-proposalSkill
- content-briefSkill
- quarter-goal-filterSkill
- win-to-anglesSkill
- activity-incentive-sprintSkill
- candidate-interview-coachSkill
- client-list-stack-pitchSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Read the draft out loud. Mark every place you stumble or take a breath mid-sentence.
- Distinctive: line 26
Keep the exceptions. Do not simplify:
- Very specific: line 30
Run the check in references/check-sheet.md and attach the pass/fail lines to the rewrite.
- Distinctive: line 35
Call scripts: read them aloud at speaking pace.
- Very specific: line 37
Before and after pairs are in references/word-swaps.md.
- Distinctive: line 49
MUST keep average sentence length at 14 words or fewer, and no sentence over 22.
- Distinctive: line 50
MUST keep every number, name and specific claim from the original.
- Distinctive: line 51
MUST read it aloud before calling it done.
- Distinctive: line 52
NEVER simplify a proper noun, a quote, or a term the reader uses daily.
- Distinctive: line 53
NEVER use a word from the swap list when the plain word means the same thing.
- Distinctive: line 54
NEVER use semicolons in outreach copy.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Applies to any copy a busy buyer will read on a phone between meetings. Produces a rewrite at a 5th-grade reading level and a short check sheet showing it passes.
Simple copy is not dumb copy. A blunt point survives at grade 5. Pretension does not.
The play
- Read the draft out loud. Mark every place you stumble or take a breath mid-sentence.
- Cut sentence length. Average 14 words or fewer. No sentence over 22. Split on "and", "which", "because" and commas.
- One idea per sentence. If a sentence holds a "which" or a "that" clause plus a second point, it is two sentences.
- Swap long words. Two syllables or fewer wherever the meaning holds. Run the swap list in references/word-swaps.md.
- Voice and rhythm. Active voice only. Contractions on. No semicolons. Few dashes. A period beats a comma, and a comma beats anything else.
- Keep the exceptions. Do not simplify:
- Proper nouns: names, companies, products, job titles.
- Terms the reader uses every day: ARR, CRM, ICP, SDR, pipeline. Match the reader. A CFO reads "EBITDA". A shop owner does not.
- Direct quotes from the prospect, a case study or a source.
- Run the check in references/check-sheet.md and attach the pass/fail lines to the rewrite.
- Branch by format:
- Cold email and DMs: be strictest here. Under 90 words for a first touch. The reader owes you nothing.
- Posts: the hook line must pass on its own. Many people read only that.
- Landing pages: headline and button text first. Body copy can run a little longer if each sentence still passes.
- Call scripts: read them aloud at speaking pace. Spoken lines should be shorter than written ones.
Before and after pairs are in references/word-swaps.md. Open them when a rewrite starts to sound childish rather than clear.
What good looks like
- First thing I check that most people skip: the longest sentence. It is almost always where the writer was hiding a point they were not sure about.
- The mediocre version: the copy is "proofread". Spelling is clean, but it still says "leverage our robust methodology to streamline your pipeline". Clean and unreadable.
- The other mediocre version: overcorrected into baby talk. Short words, but also no numbers, no names, no specifics. Grade 5 keeps the specifics.
- I know the copy is right when an 11-year-old could explain back what you offer, and the expert you are writing to does not feel talked down to.
- I know it worked when replies quote your words back to you. People only quote what they understood.
Rules
- MUST keep average sentence length at 14 words or fewer, and no sentence over 22.
- MUST keep every number, name and specific claim from the original.
- MUST read it aloud before calling it done.
- NEVER simplify a proper noun, a quote, or a term the reader uses daily.
- NEVER use a word from the swap list when the plain word means the same thing.
- NEVER use semicolons in outreach copy.
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.

