# Direct Response Copy > Use when writing or strategically rewriting a conversion-focused commercial asset. - Skill: `majesticlabs-dev/direct-response-copy` (Agent Skill) - Install (CLI): `npx skillmds@latest add majesticlabs-dev/direct-response-copy` - Raw SKILL.md: https://api.skillmd.com/api/skills/majesticlabs-dev/direct-response-copy/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: majesticlabs-dev (https://skillmd.com/u/majesticlabs-dev) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/majesticlabs-dev/direct-response-copy --- # Direct Response Copy Create persuasive copy that makes a truthful offer understandable and gives the right reader a clear next action. ## Boundary Use this skill for a complete conversion-oriented asset. - For general informational articles and guides, use `content-writer`. - For a deliberate sprint of editorial headlines or subject-line candidates, use `headline-generator`. - For a report diagnosing existing copy, use `copy-editor`. - For a clarity-only revision that does not reconsider persuasion strategy, use `prose-reviser`. Structuring the offer itself (promise, components, options, terms, risk reversal) is a separate upstream step. Express a supplied offer here; do not invent its structure. The skill must remain useful by itself. Other skills are optional next steps, not dependencies. Persuasion does not permit deception, fabricated proof, hidden material terms, false urgency, or pressure that exploits a vulnerable audience. ## Inputs Inspect supplied context before asking questions. Resolve: 1. **Reader moment:** Who sees this, what just happened, and what do they need now? 2. **Primary buyer outcome:** What practical, emotional, or economic result is supported by observed buyer behavior or verified research? 3. **Desired response:** What exact action should the reader take? 4. **Offer:** What is provided, for whom, at what price or commitment, and under what terms? 5. **Evidence:** Product facts, demonstrations, results, quotations, testimonials, limitations, and sources. 6. **Alternative:** What does the reader do today, and what cost or friction is supported by evidence? 7. **Surface:** Landing page, email, ad, CTA, product message, error, empty state, or another format. 8. **Voice and constraints:** Supplied guide, required claims, prohibited claims, legal terms, length, and channel rules. Ask once, in a concise batch, for missing information that would materially change the copy. Never invent proof, product behavior, numbers, dialogue, testimonials, customer stories, scarcity, or guarantees. ## Delivery Modes - **New asset:** Build the persuasion strategy and complete copy. - **Rewrite:** Preserve verified facts and terms while changing structure and emphasis as needed. - **File edit:** Change only requested prose; preserve metadata, links, code, data, and source notes. - **Embedded handoff:** Return only the copy needed by the surrounding workflow. Pick the mode from the request and the surrounding task rather than asking. Approval before drafting is required only when the user requests it or unresolved offer, proof, or legal choices would materially change the copy. ## Workflow ### 1. Define the reader moment and action Privately answer: - What is the reader trying to understand, avoid, complete, or decide at this moment? - What concern or objection must be resolved before the action is reasonable? - What one primary buyer outcome is supported strongly enough to organize this asset, and which secondary outcomes should remain support rather than competing promises? - What is the simplest accurate explanation of the offer? - What is the smallest useful next action? Judge copy against that moment, not against whether it sounds aggressive or clever. ### 2. Build a proof inventory Use a table when the asset has several claims: | Proposed claim | Supplied evidence | Status | Allowed wording | | --- | --- | --- | --- | | | | | | Status is one of `verified`, `qualified`, `unsupported`, or `prohibited`. Size every claim to its evidence. If proof is missing, ask for it, qualify the claim, replace it with a demonstrable fact, or omit it. Testimonials must remain faithful to the supplied wording and permission. Do not turn an ordinary comment into a result claim. ### 3. Map the value Trace each important feature through supported consequences: ```text feature -> functional change -> practical consequence -> reader value ``` Stop where evidence stops. Use buyer language only when it comes from supplied or verified research. Choose one supported endpoint as the primary buyer outcome. If evidence supports only the functional change, use that narrower result and record the broader outcome as an open gap. Do not assign a motive from a generic psychology list or invent emotional, financial, or operational outcomes merely because they would be persuasive. Quantify a problem only from supplied or verified inputs. Show assumptions when a calculation depends on them. ### 4. Choose a structure for the surface Do not force one funnel onto every asset. - **Landing page:** clear promise, reader problem, solution, proof, offer and terms, objections, CTA. - **Sales email:** relevant context, useful claim, proof, offer, one primary action. - **Ad:** one supported angle, concrete benefit, audience fit, action. - **CTA:** name the result or next step rather than a generic command. - **Error:** state what happened, what remains safe, and how to recover. - **Empty state:** explain the next action and what it enables. - **Destructive confirmation:** name the exact consequence and whether it is reversible. Omit sections that do not help the reader decide. ### 5. Draft from specifics - Put proof before adjectives when the reader is skeptical. - Prefer concrete objects, actions, constraints, and verified outcomes. - Explain benefits in the reader's context without pretending to know their feelings. - Use one primary action per surface unless multiple paths are genuinely required. - Make price, commitment, limitations, eligibility, and material conditions visible. - Use urgency or scarcity only when it is true, current, and relevant. - Disqualify readers only for legitimate fit or safety reasons, not to manufacture exclusivity. A story is usable only when its facts, attribution, and publication rights are supplied. If no true story is available, use a plain factual angle. ### 6. Validate Read the copy as a skeptical buyer. Beyond the Quality Gate below, verify: 1. The copy distinguishes benefits from guarantees. 2. The voice fits the reader moment and channel. 3. The CTA accurately describes what happens next. 4. No fabricated proof, testimonial, urgency, or personal story appears. Whatever this pass changes must go back through the proof inventory before it ships. ## Output Lead with the complete requested asset. Follow it with: ```markdown **Reader moment:** [who sees this and what just happened] **Primary buyer outcome:** [the one supported result organizing the asset] **Desired response:** [the exact action] **Proof used:** [each material claim and the evidence that permits it] **Open gaps:** [unresolved proof or approval blockers, or "none"] ``` Add variants only when the request benefits from comparison. For embedded handoff or copy-only requests, return only the finished copy. ## Quality Gate The copy is ready when: - the reader can understand the offer and next action without decoding jargon - one primary buyer outcome organizes the asset and is no stronger than its proof - claims are no stronger than their evidence - proof and material limitations are easy to find - persuasion serves an informed decision rather than manipulating attention - the surface follows its real channel constraints - the asset is complete without requiring another installed skill