skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
boringmarketer/boring-marketing-skills110 installs

direct-response-copy

Write copy that converts (landing pages, sales pages, emails, ads, headlines, CTAs) in the customer's own words, matched to the ad or email that sends the traffic. A claim gate keeps every shipped line to verified facts (stronger ideas go on a To make this true list), and a private score-and-rewrite loop lifts the draft. Includes local-service patterns for copy that makes the phone ring. Approved page copy hands off to /landing-page to build. Use when someone needs to sell in writing, wants copy scored, or has ads that get clicks but no sales or calls.

How do I install this agent skill?

npx skills add https://github.com/boringmarketer/boring-marketing-skills --skill direct-response-copy
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill is designed for writing marketing copy and is generally secure. It includes a surface for indirect prompt injection as it retrieves content from external URLs for market research. It also executes a local Python script for configuration, which is a standard pattern for this developer.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

Direct Response Copy

Copy that converts sounds like a smart friend explaining something they figured out, while it quietly answers every doubt the reader has. This skill writes that copy in the customer's own words, matches it to whatever sent the reader, keeps every claim to what the business can back, and scores it privately before it ships. It's a floor, not a ceiling. When the situation argues for a better path, take it and say why.

Frameworks (awareness levels, Schwartz, Caples, the seven scoring dimensions) are for thinking. The copy, the notes and the chat summary say things in plain words, and scores never appear in the deliverable unless the user asked for a score.

Context

Only if ./brand/, ./brands/ or MARKETING.md exists (nothing to load otherwise), run: python3 ${CLAUDE_SKILL_DIR}/../start-here/scripts/brand_context.py --for direct-response-copy (${CLAUDE_SKILL_DIR} is this skill's folder; outside Claude Code use the folder this file was read from, e.g. .agents/skills/direct-response-copy. If the script or python3 is unavailable, read the brand folder directly: ./brands/<slug>/ when ./brands/active names one, else ./brand/; then MARKETING.md, preferences.md and the files in reads:. If none exist, proceed standalone and ask only for the offer, who it's for, and what proof exists.)

If learnings.md holds relevant priors (headline patterns, offers, past test results), apply them and say which: "Applied: price-led headlines beat speed-led on your March service pages."

Entry points

RequestPath
New copy (default)Phases 0 to 5; for pages, then offer the /landing-page handoff
"Score this" or "why isn't this converting"Load the copy and references/calibration-anchors.md, score, give the scorecard and the top fixes. Rewrite only if asked. A live URL goes to /landing-page TEARDOWN; a local business's phone-first check goes to /first-screen-check
Single quick asset (5 subject lines, one ad, a headline and first screen)Quick Mode: skip the Phase 0 fan-out, brief.md and ./brand/assets.md; generate, run the gate once, save the copy file, deliver
"Build the page" (copy approved)Route to /landing-page BUILD FROM COPY

Iteration: if ./campaigns/{name}/ already holds copy, read it first and ask: revise, add a piece, or start fresh. When revising, score the existing copy first so the rewrite targets real weaknesses.

Phase 0. Find the words before writing any

Robert Collier's rule: enter the conversation already going on in the reader's mind. The best headlines are usually found, often verbatim, in customer language.

  1. Read ./brand/voc.md and positioning#chosen-angle if they exist. Pull verbatim pains, desires and objections. "I'm doing my books at midnight on the 30th" is a headline; "users struggle with bookkeeping" is not.
  2. If voc.md is absent and a product URL exists, run a quick parallel pass, 2-3 subagents at once: the product or service page (claims, pricing, mechanism, who it's for); 1-2 competitor pages (the saturated promises your copy must not sound like); one review source that fits (G2, an app store, Amazon or a Reddit thread for products; Yelp, BBB or review snippets for a local business). Each returns verbatim quotes with URLs, not prose. WebFetch and WebSearch do this for free. We use Firecrawl to read the pages in full (free tier of 1,000 credits a month, no card) and Exa to find the competitor and review pages a keyword search misses (free tier, then pay as you go). Without them the free tools read what they can reach. Park findings in ./campaigns/{name}/brief.md (full runs only).
  3. If neither exists, write from the user's input, label the deliverable Data: MODEL KNOWLEDGE (verify claims before spending), and suggest /audience-research to build voc.md. Point at preferences.md or MARKETING.md for banned words by name; never restate a banned phrase.

Label mined deliverables Data: LIVE (n sources).

Phase 1. Frame the job

First time? references/worked-example.md shows three before-and-afters (a local service, a SaaS, a coach) so you can see the bar. Establish five things. Ask only for what's missing.

Format. Landing page (one offer, one primary CTA, scannable), sales page (long-form, story-driven, full objection handling), email (one idea, one CTA, the subject line is the headline), ad, social post, text message, or other. For ads and social, don't trust remembered character limits: pull current limits from voice-profile#platform-adaptations or ./brand/algo-cache.md, and refresh per its TTL if stale.

Where the reader came from, and what they were promised. A reader arrives carrying a promise from the ad, email, post or search that sent them. The first screen has to repeat that promise in the same words, or they leave. Get the ad text, keyword, subject line or post, and write the headline to match it. Local businesses miss this constantly. In a check of local sites on a phone (Nov 2026), most businesses running ads that promise 24/7 or same-day service didn't say it on the first screen of the page the ad opens.

Awareness level (Schwartz). This decides the lead:

LevelThey knowLead with
1 Unawarenothingidentity, emotion, story
2 Problem-awarethe painthe problem named vividly, then that a fix exists
3 Solution-awarefixes existyour unique mechanism
4 Product-awareyour productdifferentiation, proof, objections handled
5 Most-awarethey want itthe offer itself

Less aware means longer copy. Most-aware means get out of the way.

The so-what chain. Ask "so what?" of every feature until you reach time, money or worry, usually three levels down: "automatic reminders" so "invoices get paid without you asking" so "you stop sending awkward emails to clients you like". Write from the bottom.

Fact sheet and proof inventory. List every fact the copy may use, each with its source: the brief or the user's messages, the business's site, its reviews, or research you verified. Then what proof exists: testimonials, data, case studies, review counts, photos, credentials. Never write a claim bigger than its proof. If the proof is thin, the copy gets quieter, not louder. Pull the angle from positioning#chosen-angle; if none exists and the market is saturated, suggest /positioning-angles first.

The claim gate (hard rule)

Shipped copy (headline, subhead, body, bullets, offer, guarantee, the line under the CTA) uses only facts on the fact sheet.

  • A named mechanism or guarantee comes from what the business does today. Never invent a method to explain why it works, and never write a guarantee the business doesn't offer because the page would be stronger with one.
  • Nothing that doesn't exist yet. No feature, option, setting or policy the business hasn't shipped: no picker, no one-click skip, no "cancel anytime" unless it's true.
  • Keep the facts exact. "22 techs" never becomes "22 licensed plumbers"; "most jobs" never becomes "every job"; a 4.8 stays a 4.8.
  • From positioning.md, use what Chosen Angle states as current. Anything under "Not yet true" stays out of the copy.
  • Bold ideas still get said. When the strongest copy needs something the business doesn't do yet, write the shipped copy from facts and add a To make this true list after it: the idea, the line it would unlock, and what it takes (a build, a policy, a number to check, the owner's sign-off).

A claim with no source is cut or moved to that list. Calling a claim "assumed" or "illustrative" inside shipped copy doesn't make it shippable.

Phase 2. Write

Explain it like you would to a smart friend who's skeptical but curious, back every claim with a specific, and make the after-state something they can picture. For pages, load references/block-grammar.md (what each section owes the reader). For long-form or deep headline sessions, load references/COPYWRITING_PLAYBOOK.md (the masters' formula banks). For a local business, also load references/local-patterns.md.

Headlines

One headline can outpull another by 19.5 times on the same offer (Caples). The master formula: [action verb] + [specific outcome] + [timeframe or contrast], as in "Ship in days, not weeks". The working patterns:

  • Specificity: a number plus an unexpected detail (Ogilvy's electric clock). Show it and the reader persuades themselves.
  • Story: "They [doubted] when I [action]... but when I [result]" (Caples' piano ad).
  • Question: "Do you [common struggle]?" Self-selects the right reader.
  • Transformation: "From [bad state] to [good state]."
  • Contrarian: challenges a belief they already half-doubt. It must pay off.
  • Customer quote: the reader's own sentence from voc.md, lightly trimmed.

Headlines fail by being clever instead of clear, vague instead of specific, about the company instead of the reader, or by leaving nothing to find out.

Openings, loops and flow

The first sentence gets the second one read. Working moves: the direct challenge, the in-scene story, the confession, the specific result, the question that matches their reality, the short plain sentence. Banned: "In today's fast-paced world", "Are you ready to take X to the next level?", "Look no further", "Let's dive in", and anything that fits any business.

Open loops pull readers forward ("the third one is the reason people switch"); close every loop you open, small ones within a few paragraphs. Vary rhythm: a short hook, a longer sentence that breathes, a short landing. Momentum killers are jargon, wall paragraphs, tangents and identical sentence shapes back to back.

Pain in numbers

Quantified problems feel solvable and purchasable: "4 hours on setup + 6 on the page + 4 on webhooks = 14 hours before you've sold anything." Or the lived scene that makes them feel it. Numbers about the business must be its real ones. A scenario framed as one ("say you send 20 invoices a month") is fine.

Proof, stories and disqualification

  • Testimonials are mini case studies: before state, action, specific result, time, reaction. "Invoiced 9 clients in the time my spreadsheet took for 2" beats "great product". Never write one; quote real ones with permission.
  • The founder story (humble start, struggle, discovery, result, offer) is the highest-trust element on a creator or founder page. Get the real story; don't invent it.
  • Disqualification ("not for you if...") raises the credibility of everything else. Include one item that costs you customers.

CTAs

Weak CTAs command ("Submit", "Learn more"); strong ones say what happens ("Send me the first lesson", "Get my price in 2 minutes", "Call now, a person answers"). Under the CTA, one friction reducer that removes the live objection: the guarantee, the count, the time, "no card needed". Repeat the same CTA wording down the page.

Voice and AI tells

Load the brand-voice skill's references/ai-tells.md if the voice profile is in play. On top of it, cut the copy tells: "unlock", "unleash", "supercharge", "game-changer", "we pride ourselves", "your trusted partner", fake urgency, hedged claims, every bullet starting the same way, no contractions. Read it aloud. If it sounds like "writing copy" instead of a person talking, rewrite that part.

Local service businesses

For plumbers, roofers, HVAC, dentists, med spas, cleaners and anyone customers call from a map, references/local-patterns.md carries the full pattern bank. The decisions that change:

  • The headline names the service and the place, then makes one promise on one of five levers. Speed ("Water heater replaced today in Dallas. Call by noon."), price clarity ("$____ installed. The price we quote is the price you pay."), guarantee ("On time, or the trip is free."), proof ("4.9 from 1,200 Dallas homeowners", real count only), and service area ("Plumbers for Lake Highlands and Lakewood"). Use a lever only when the business already delivers it; the claim gate applies. Price clarity is the lever most often missing. In a Housecall Pro survey of 1,040 US homeowners (Oct 2025, vendor data), 97% said transparent pricing matters when hiring a pro and 77% named hidden or surprise costs as a top frustration.
  • The first screen on a phone carries the argument: service and area, the promise, proof, and tap-to-call with the number visible. "Licensed, insured, family owned" sits under it as small text, never as the headline.
  • Job type sets the length. Emergency copy is short (nothing to read before the number); urgent jobs need the price, the arrival window and reviews; planned projects need the method, proof of similar jobs, warranty, financing and an FAQ.
  • The CTA is usually the call, with text as a second option for people at work.
  • Testimonials carry first name, last initial and neighborhood, and name the before, the time and whether the price matched the quote.

Phase 3. Variants

Generate variants by default (a tight single-asset ask can skip them; say so).

Headlines: 5-10, spanning frameworks (direct benefit, curiosity, proof, contrarian, story, customer quote; for local, the five levers) plus hybrids. Numbered, the pick starred, led by a Quick Pick:

QUICK PICK
★ "{headline}"
  → Best for: {who's reading and where they came from, in plain words}
  → Why: {one sentence}
See all {N} variants below.

Every variant passes the claim gate; a variant that only works with an unbuilt feature belongs on the To make this true list, not in the set.

Body: 2-3 variants for pages. A, the control (the straight version of the angle). B, contrarian or risk-reversal lead (best for skeptical readers and saturated markets). C, proof-led (strongest evidence first; best for product-aware readers and planned purchases). One note after each: angle, best for, recommended test.

Email subject lines: 5-7 (direct benefit, curiosity, story teaser, question, contrarian). Star the pick. Ads: one set per hook, with the landing page headline it must match noted beside each.

Phase 4. The gate

The claim check runs first and is pass or fail. Put the fact sheet beside the copy. Every claim in the headline, subhead, body, offer, guarantee and CTA line traces to a fact. One unsourced claim fails the gate whatever the score: cut it or move it to To make this true.

Load references/calibration-anchors.md before scoring. Scores without anchors drift toward flattery. Score the recommended variant 1-10 on seven dimensions:

DimensionQuestion
ClarityDoes a distracted reader get the core message in one pass?
SpecificityReal numbers, named details, concrete mechanisms?
VoiceOne identifiable human, or a committee?
DesireIs the after-state a moment they can picture, not an adjective?
ProofIs every claim covered by evidence that exists?
UrgencyIs there an honest reason to act now?
FlowDoes each line pull to the next, headline to CTA?

No proof yet (a new offer): score Proof n/a, keep claims as quiet as the evidence, and judge the other six against 48/60.

The loop: if any dimension is below 7 or the total is below 56/70, rewrite only the weak dimensions and rescore. About three passes is the ceiling; past that the constraint is the offer or the proof inventory, so say so in one plain line. Never invent scarcity to lift Urgency (a quiet cost-of-inaction line scores 6-7, and that's fine), and never score Proof on evidence the user hasn't provided.

Scores stay out of the deliverable. The score table and its history go in brief.md (full runs) and nowhere else. The copy file and the chat summary carry the copy, the To make this true list and a short evidence note. "Score this" requests are the exception: there the scorecard is what was asked for.

Promise-match check (pages, ads and emails that link to pages): put the source (ad, email, post) beside the page's first screen. The offer and the promise appear in the same words. A mismatch fails the gate whatever the score.

Phase 5. Write for the AI reader too

Buyers ask an assistant "is this legit?" or "how much should this cost?" before buying, and the assistant reads the page. It keeps facts and drops adjectives, so copy built on adjectives summarizes to nothing.

  • Make every major claim survive paraphrase: specific, verifiable, mechanism attached. "Median invoice paid in 9 days (n=1,400 users)" survives; "lightning-fast payments" evaporates. Cite a source inline for big claims.
  • Write the FAQ for the objections an assistant would surface: real pricing, refund or cancellation terms, who it's not for, how it compares to the obvious alternative. For a local business: trip fees, how soon, what's guaranteed, the areas served, financing.

A/B testing

Suggest 2-4 tests. Priority order: headline, offer framing, proof structure, CTA, body. One variable per test. Under about 1,000 visitors a week, small refinements never reach a readable result, so test big swings only (a different angle or lead) and say so plainly. Measure the action that pays (sales, sign-ups, calls and form fills for local), not clicks. Never project impact numbers; state the hypothesis and the metric.

From copy to page

Page architecture and the build live in /landing-page. After page copy passes the gate, offer the handoff and pass forward the copy file path, the awareness level or job type, the traffic source with its ad text, and the variant list. The copy file is the contract; the build is diffed against it.

Output

Files first, summary second, per start-here/references/output-format.md (deliverable header, content, Files saved:, What's next:). The content is the copy itself, then To make this true (when there is one), then a short evidence note: what the claims rest on (the brief, the site, n reviews, dated sources) and anything the user should verify before it goes live. No score tables, framework labels or script paths.

./campaigns/{name}/
├── brief.md          # full runs only: angle, awareness level, traffic source and its
│                     # promise, VoC evidence, fact sheet, score history (working file)
└── landing-page.md   # or sales-page.md / emails/{subject-slug}.md /
                      # ads/{platform}-{variant}.md / social/{platform}-{desc}.md

Each copy file gets frontmatter: type, campaign, awareness_level, traffic_source, variant, word_count, date (handoff fields for /landing-page; the score lives in brief.md). Append one line per asset to ./brand/assets.md (not in Quick Mode).

What's next (pick 2-4):

  • After page copy: /landing-page to build and ship it (~15 min); for a local business, /first-screen-check once it's live (~10 min)
  • After ad copy: /paid-ads for platform packaging and the test plan (~15 min)
  • After any copy that captures leads: /email-sequences for the follow-up (~15 min)
  • Once real numbers exist: /performance-review to turn the predictions in brief.md into priors

When the user edits your work

Apply the edit, then make it stick: save a gold case to ./brand/gold/<this skill>/ and one to three yes/no checks to ./brand/checks.md, and confirm in one line. Before handing over any work, answer the checks the context block loaded, silently, and fix every no. How: ${CLAUDE_SKILL_DIR}/../start-here/references/taste-loop.md.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/boringmarketer/boring-marketing-skills/direct-response-copy">View direct-response-copy on skillZs</a>