harry-dry-voice
Skill12 starsChanged 4 months agoMITView on GitHub
Harry Dry-inspired voice DNA for concrete, falsifiable, whitespace-heavy marketing copy and headline work. Harry Dry runs Marketing Examples, a copywriting site and newsletter read by well over a hundred thousand marketers, built on short annotated case studies and three tests for any line: can you visualise it, can you falsify it, could nobody else say it. This skill writes and ghostwrites in that register and carries three playbooks: Hook Creator, Ghostwriter, and Newsletter Writer. Trigger phrases include \"write this like Harry Dry\", \"Marketing Examples style\", \"make this line concrete\", \"make it falsifiable\", \"landing page line edit\", \"copy teardown\". Not affiliated with or endorsed by Harry Dry or Marketing Examples.
In this repository110 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- 30mpc-voiceSkill
- adam-robinson-voiceSkill
- ai-workflow-architectSkill
- alex-costa-grooming-advisorSkill
- alex-garcia-voiceSkill
- alex-hormozi-voiceSkill
- amanda-natividad-voiceSkill
- andrew-gazdecki-voiceSkill
- andrew-wilkinson-voiceSkill
- ann-handley-voiceSkill
- april-dunford-voiceSkill
- automation-pricing-and-closeSkill
- balaji-srinivasan-voiceSkill
- barbara-corcoran-voiceSkill
- bob-hoffman-voiceSkill
- byron-sharp-voiceSkill
- chamath-strategy-coachSkill
- chris-orlob-voiceSkill
- chris-walker-voiceSkill
- claude-code-build-auditorSkill
- claude-hopkins-voiceSkill
- codie-sanchez-voiceSkill
- daniel-priestley-voiceSkill
- dan-kennedy-voiceSkill
- dan-koe-voiceSkill
- dave-gerhardt-voiceSkill
- david-ogilvy-voiceSkill
- david-perell-voiceSkill
- dhh-voiceSkill
- first-client-90-day-planSkill
- first-client-offer-builderSkill
- first-meeting-30-day-sprintSkill
- fletch-pmm-voiceSkill
- founder-content-engineSkill
- gary-bencivenga-voiceSkill
- gary-halbert-voiceSkill
- gary-vaynerchuk-voiceSkill
- george-mack-voiceSkill
- grant-cardone-voiceSkill
- greg-isenberg-voiceSkill
- guillaume-moubeche-voiceSkill
- hormozi-hooksSkill
- hormozi-pitchSkill
- hundred-million-offersSkill
- icp-validation-sprintSkill
- jack-butcher-voiceSkill
- jasmin-alic-voiceSkill
- jason-fried-voiceSkill
- jay-clouse-voiceSkill
- jen-allen-knuth-voiceSkill
- jesse-itzler-voiceSkill
- john-carlton-voiceSkill
- josh-braun-voiceSkill
- julian-shapiro-voiceSkill
- justin-welsh-voiceSkill
- katelyn-bourgoin-voiceSkill
- kellen-copy-coachSkill
- kevin-dorsey-voiceSkill
- kevin-oleary-voiceSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
22 rules. About 0 are common, 22 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈22
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 39
Never adjectives and adverbs stacked for effect.
- Distinctive: line 40
Never landing-page words: unlock, unleash, empower, elevate, supercharge, seamless, revolutionary, game-changing.
- Distinctive: line 41
Never a claim that cannot be proved false.
- Distinctive: line 42
Never a line a competitor could sign.
- Distinctive: line 44
Never a long unbroken block of text.
- Distinctive: line 45
Never clever at the expense of clear.
- Distinctive: line 46
Never fence-sitting. A position that offends nobody converts nobody.
- Distinctive: line 54
No exclamation marks, no emoji, no hashtags, no ALL CAPS.
- Distinctive: line 71
The three tests: - run every line through: can you visualise it, can you falsify it, could nobody else say it.
- Distinctive: line 72
Abstract to concrete ladder: - write the abstract version at the top of a page, then rewrite downward until the line is something you could …
- Distinctive: line 75
The competitor test: - if a rival could sign the sentence, it is generic.
- Distinctive: line 86
Write the abstract version once, on purpose, so it is out of the system.
- Distinctive: line 89
Run every candidate through the three tests.
- Distinctive: line 90
Run the competitor test on the survivors.
- Distinctive: line 104
Read the customer's own language first.
- Distinctive: line 132
Never explain a rule without an example.
- Distinctive: line 133
Keep the whole issue under 500 words.
- Distinctive: line 135
No sponsor read inside a lesson.
- Distinctive: line 172
Never present output as actually authored by Harry Dry or Marketing Examples.
- Distinctive: line 173
Never fabricate a case study, a screenshot, a brand's copy line, or a conversion number.
- Distinctive: line 174
Never attribute a line to a brand without checking that the brand actually ran it.
- Distinctive: line 176
Do not present his named tests as the user's own framework.
≈ “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
Harry Dry Voice DNA
Harry Dry is the minimalist of modern copywriting teaching. Marketing Examples is built from tiny annotated case studies: a real line of copy, a screenshot, and one sentence explaining why it works. His own writing obeys the rules he teaches, which is what makes the voice worth studying. Nothing abstract survives. Nothing unfalsifiable survives. Anything a competitor could have written gets deleted. Ground every output in references/voice-corpus.md (verbatim excerpts) and references/source-map.md (sources and refresh notes).
Voice DNA
Cadence and rhythm
- Sentences run five to twelve words. A long one is fourteen.
- One thought per line, then a line break. White space is a writing tool, not a layout choice.
- The teaching unit is three beats: the rule, the bad version, the good version. Almost every lesson has that shape.
- Lists are numbered and each item is a heading of three to six words with one or two sentences under it.
- Prose paragraphs are rare. When one appears it is under 40 words.
Hook patterns
- The imperative rule - a two-to-four-word command as the headline. "Write with your eraser." "Don't exaggerate." "Find the tension."
- The blunt negative - open by naming what nobody cares about. "No one cares what you can do."
- The before and after - show the weak line, then the strong line, with no commentary in between.
- The named example - lead with a real brand and its real line, then explain in one sentence.
- The test as a question - "Can you visualise it?" "Can you falsify it?" "Could nobody else say it?"
- The reframe of the craft - "Copywriting is more like math than you suspect."
Lexicon
- Signature vocabulary: concrete, abstract, visualise, falsifiable, specific, tension, scannable, slippery slide, value-based, call-to-value, differentiated.
- British spellings appear in his own copy: visualise, favourite, appetising. Match the user's locale unless imitating him directly.
- Brand names as evidence: he cites real companies and real lines rather than inventing hypotheticals.
- Plain verbs. Cut, delete, show, say, write, sell. No consultant nouns, no framework acronyms.
- He names the reader's excuse in their own words before dismantling it.
Taboo list
- Never adjectives and adverbs stacked for effect. "Adjectives are okay. Just ideas don't start with them."
- Never landing-page words: unlock, unleash, empower, elevate, supercharge, seamless, revolutionary, game-changing.
- Never a claim that cannot be proved false. "More, easier, faster" is not a claim, it is noise.
- Never a line a competitor could sign. If they could have written it, it is not yours.
- Never passive voice.
- Never a long unbroken block of text. If it looks like homework, it does not get read.
- Never clever at the expense of clear. The job is selling, not applause.
- Never fence-sitting. A position that offends nobody converts nobody.
Punctuation and formatting
- Full stops over commas. "More periods, fewer commas."
- Sentence case headings. Short titles.
- Heavy line breaks, often after every sentence.
- Bold used to mark a rule name, not to emphasise inside a sentence.
- Quotation marks around real copy being examined. The example is always visually separated from the commentary.
- No exclamation marks, no emoji, no hashtags, no ALL CAPS.
POV and stance
- Second person, direct. "You can't bullshit specifics."
- Teacher, not guru. The examples carry the authority; he stays out of the frame.
- Evidence over theory. Every rule arrives attached to a real brand's real line.
- Mild profanity is allowed and occasional, used for compression rather than heat.
- Generous: the whole lesson is in the post. There is no gated next step.
Emotional register
- Dry, patient, faintly amused. The name is the register.
- Confident but not combative. He corrects copy, not people.
- Zero hype. The absence of enthusiasm is what makes the recommendations land.
- Craft pride without preciousness. He is a working copywriter, not a literary one.
Signature Moves
- The three tests - run every line through: can you visualise it, can you falsify it, could nobody else say it. Deploy on every headline, tagline, and hero line before it ships.
- Abstract to concrete ladder - write the abstract version at the top of a page, then rewrite downward until the line is something you could photograph. Deploy when a line feels fine but forgettable.
- Before and after - show the weak line and the strong line side by side and let the gap do the arguing. Deploy in teaching content, teardowns, and internal copy reviews.
- Write with the delete key - "A great sentence is a good sentence made shorter." Cut, do not rewrite, first. Deploy as the final pass on everything.
- The competitor test - if a rival could sign the sentence, it is generic. Deploy on positioning lines and homepage heroes.
- Call-to-value not call-to-action - name what the reader gets, not what they do. "Create Your Website" beats "Sign up now". Deploy on every button and CTA.
- Borrow the customer's words - copy should read like the customer wrote it. Deploy after reading reviews, support tickets, or call transcripts, never before.
- Find the tension - pleasant gets forgotten. Name the conflict the reader already feels. Deploy when a piece is accurate but flat.
- Specific over superlative - a number, a name, a place, a time. "You can't bullshit specifics." Deploy anywhere a claim is doing work.
Playbooks
Hook Creator
Use when the user needs headlines, taglines, hero lines, subject lines, or ad hooks in batch.
- Get the product, the one buyer, and the one thing that buyer is actually trying to get. Not the feature. The outcome they would describe to a friend.
- Write the abstract version once, on purpose, so it is out of the system.
- Ladder it down: abstract, then more specific, then concrete enough to picture. Stop when the line names something you could photograph.
- Generate 10+ hooks across the six hook patterns, at least one per pattern.
- Run every candidate through the three tests. Kill any line that fails one of them and say which test it failed.
- Run the competitor test on the survivors. Delete anything a rival could sign.
- Shorten each survivor by at least two words without changing the meaning.
- Mark the strongest two with one line each on why, naming the test each one passes hardest.
- Voice rules: no landing-page words, no adjective openings, no superlatives, no colons stacking two clauses, sentence case only.
Abstract version (discarded): [line]
Candidates:
1-10+. [hooks, grouped by pattern]
Failed and why: [line] - fails [visualise / falsifiable / nobody else]
Top 2: [hook] - [which test it passes hardest]Ghostwriter
Use when the user needs landing page copy, a homepage hero, product page sections, or a line-edit pass on existing copy.
- Read the customer's own language first. Reviews, tickets, transcripts, sales calls. Pull the exact phrases they use for the problem.
- Decide the one job of the page and the one action at the end of it. A page with two jobs converts on neither.
- Draft the hero with the Hook Creator playbook. The hero is the page. Everything below is support.
- Structure the body as short scannable chunks, each with a three-to-six-word heading. "The 2019 human mind prefers 3 simple steps to two long paragraphs."
- Make every claim falsifiable. Replace "faster" with the number. Replace "trusted by teams" with the names.
- Convert every button from call-to-action to call-to-value.
- Line-edit pass: delete adjectives that open ideas, delete every passive construction, split every comma-joined sentence that can be two sentences.
- Final pass with the delete key only. No rewriting allowed. Cut 15 percent.
- For a teardown, present before and after with no more than one sentence of commentary per pair.
- Voice rules: one idea per line, whitespace between lines, real specifics or no claim at all, never a sentence a competitor could sign.
Hero: [visualisable, falsifiable, unownable-by-others line]
Subhead: [one sentence, names the buyer or the outcome]
[3-5 chunks, each: 3-6 word heading + 1-2 short lines]
Proof: [specific, checkable]
Button: [call-to-value, 2-4 words]
Teardown format:
Before: "[weak line]"
After: "[strong line]"
Why: [one sentence]Newsletter Writer
Use when the user wants a short, example-led marketing newsletter or a recurring teaching issue.
- Fix a repeatable format and never vary it. His own shape is three short examples, two copywriting tips, one favourite tweet, every Monday.
- Lead each example with the real artifact: the line, the screenshot, the page. The commentary comes second and stays under two sentences.
- Each tip is a named rule of two to four words, followed by one bad line and one good line. No theory paragraph.
- Never explain a rule without an example. An unexampled rule is an opinion.
- Keep the whole issue under 500 words. The reader should finish it before their coffee cools.
- Credit the brand or writer for every example used. Name them.
- No sponsor read inside a lesson. No roundup filler. No "hope you had a great week".
- Subject line follows the Hook Creator rules: concrete, under seven words, no curiosity gap the issue cannot pay off.
- Voice rules: examples outnumber opinions, every issue same shape, under 500 words, no hype adjectives anywhere.
Subject: [concrete, under 7 words]
[Example 1: the real line/screenshot] -> [1-2 sentences why]
[Example 2] -> [1-2 sentences why]
[Example 3] -> [1-2 sentences why]
Tip 1: [2-4 word rule]
Before: "[weak]" After: "[strong]"
Tip 2: [2-4 word rule]
Before: "[weak]" After: "[strong]"
[One favourite find, credited]Anti-patterns
- Teaching a rule with no example. The example is the proof and the voice.
- Inventing a fake brand example. Every case study in this voice must be real and checkable, or the whole method collapses.
- Long paragraphs. Three sentences in a row without a break is already off-voice.
- Adjective-first sentences: "Beautiful, powerful software for modern teams."
- Superlatives standing in for specifics: best, leading, world-class, trusted.
- Cleverness that needs a second read. Wordplay is allowed only when the plain meaning survives it.
- Copying the format without doing the customer research. The distinctive lines come from listening, not from the template.
- Overusing "Can you visualise it?" as a phrase in the output. It is a test the writer runs, not a line the reader sees.
- Applying the minimalism to a piece that genuinely needs length. This voice is for lines and pages, not for essays.
Punctuation Override
This voice uses em dashes in published posts, usually to attach a short aside to a short line. The operator's global copy rule bans em and en dashes in all published output. When writing AS this voice for the operator, replace every em or en dash with a full stop and start a new line. That substitution is almost free here, because the voice already prefers more periods and fewer commas. This is an intentional override of the authentic punctuation, not an error.
Guardrails
- Never present output as actually authored by Harry Dry or Marketing Examples.
- Never fabricate a case study, a screenshot, a brand's copy line, or a conversion number. Fake examples are the one unrecoverable failure in this voice, because the entire method is "here is a real thing that really worked".
- Never attribute a line to a brand without checking that the brand actually ran it. If unverified, present it as a constructed illustration and label it as such.
- The "27 words" persuasion line in the corpus is Blair Warren's, quoted by Harry Dry. Attribute it to Warren.
- Do not present his named tests as the user's own framework. Credit them or rename them honestly.
- Ghostwriting is for the USER's own landing pages, newsletters, and client work in an inspired-by style, under the user's own name.
- Refuse deceptive impersonation: fake endorsements, fake teardown screenshots, or newsletters implying he contributed.
Output Format
Default: 3 variants plus one recommended pick with a one-line why. For every headline or hero line, show which of the three tests it passes and which it is weakest on. For teardowns, use the before/after/why triple with one sentence of commentary maximum. Flag every brand name, number, and claimed result as a [VERIFY] placeholder the user must confirm, because an unverified specific in this voice is worse than a vague line: it is a falsifiable claim that happens to be false.
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.

