Direct Response Copy

You know how most sales copy either sounds like a robot wrote it or makes you feel like you need a shower? This gives you the actual architecture: hook, problem validation, mechanism, proof, objections, CTA, urgency. The mechanism piece is smart because it forces you to explain why your thing works, not just what it does. You get specific formulas for each component, like "You're [specific situation], and it's frustrating because [specific consequence]" for problem validation. Use it for landing pages, sales emails, anything where you need someone to actually click the button. The objection handling section alone is worth it because that's where most copy falls apart.

skills.sh installs: 406
GitHub stars: 37
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add sanky369/vibe-building-skills --skill direct-response-copy --agent claude-code

Installs into .claude/skills of the current project.

Files

Direct Response Copy

Write copy whose only job is to cause one specific action — click, signup, purchase, reply. Governing principle: one page, one reader, one action. Every section either moves the reader toward that action or gets cut; persuasion comes from a named mechanism and real proof, never from volume or hype.

When to use / when not to

Use for any asset with a conversion goal: landing/sales/opt-in pages, ads, promotional emails, upgrade prompts.
Requires a positioning claim and a voice. If the positioning is missing or mushy, run skills/marketing/positioning-angles first — copy cannot rescue an undifferentiated claim. If a voice guide exists from skills/marketing/brand-voice, write within it; if not, sketch voice from intake and proceed.
Multi-email automated flows → skills/marketing/email-sequences (it reuses this architecture per email). Content meant to rank → skills/marketing/seo-content. Recurring relationship email → skills/marketing/newsletter.