skills/copy-interview/SKILL.md
Extract authentic marketing copy by interviewing the user as a buyer would, then analyze the output line-by-line. Use when the user says 'interview me for copy,' 'extract copy,' 'help me write copy by interviewing me,' 'copy interview,' 'what would I say about this offer,' or 'help me pitch this.' Combines buyer-perspective interviewing (inspired by Jason Adams' method) with line-by-line copy analysis and direct response principles.
npx skillsauth add skinnyandbald/fish-skills copy-interviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Extract authentic marketing copy through a structured buyer interview, then refine it using line-by-line analysis.
Arguments: $ARGUMENTS
Your verbal pitch is always better than what you write from a blank page. This skill gets you talking naturally by simulating a real buyer conversation, then turns that raw material into polished copy.
.claude/skills/voice-guide/style-guide.md -- this is the voice bible.claude/product-marketing-context.md if it existsAsk the user (or infer from arguments):
If the user provides a page URL or file path, read it first.
You are now a prospect. Not a copywriter, not a consultant -- a skeptical buyer who's interested but not sold. Your job is to push until the user gives you their most authentic, compelling language.
Ask one question at a time. Wait for the answer before asking the next.
These are not a rigid script -- adapt to what the user says. But cover these angles:
Opening (get them talking naturally):
"Tell me why I should buy [the thing]. Like straight up, just to me. Don't sell it -- just tell me."
Price objection (forces value framing):
"That seems like a lot of money. What do you think?"
If they rationalize with hourly comparisons or competitor pricing, push back:
"I don't care what McKinsey charges. What's it worth to ME? What happens if I don't do this?"
Trust objection (extracts credentials):
"How can I be sure this will actually help me?" "Why else should someone trust you?"
Deliverable clarity (gets specific):
"What exactly will I get?" "And then what happens after that?"
Outcome vision (the aspirational close):
"If this goes really well, what's the best thing that can happen for me?"
Differentiation (separates from alternatives):
"How is this different from [obvious alternative]?"
The meta-question (if they're hedging):
"You sound like you're being careful not to oversell. But I need to feel confident enough to spend money. Can you tell me the version where you're proud of what this does?"
Take the raw material from the interview and write the copy. Rules:
After drafting -- or when reviewing existing copy -- run this analysis:
Read each line of the copy individually. After each line, answer two questions:
| Reader reaction | Grade | Action | |----------------|-------|--------| | "Hell yeah, exactly" | Keep | This line is working | | "Interesting, tell me more" | Keep | Momentum is good | | "Is that true?" / "Do I believe that?" | Rewrite | Making them think, not feel | | "So what?" / skimming | Rewrite | Not earning attention | | "This feels like AI" / "This feels corporate" | Rewrite | Lost the authentic voice | | "F*ck this guy" (if CEO sends to CTO) | Delete | Alienating the wrong people |
Spend the most time on these, in this order:
Present the draft with:
Ask: "Read through this. Flag anything that doesn't sound like you, anything that sounds like AI, or anything where you'd say it differently."
development
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
tools
Verify worktree plugin patches are intact after plugin updates. Checks compound-engineering and superpowers skills for Claude Code launch instructions.
development
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
development
Reviews the feature you just built and adds missing test coverage. Focuses on behavior that matters — not coverage metrics. Use after completing a feature to identify untested code paths, edge cases, and risk areas.