Convert Proof
Apply Conversational Proof to any claim: claim → evidence → reason → move-on pattern...
Install
npx skills add FerroxLabs/wayland --skill convert-proof -g -a claude-code -y- Repository
- FerroxLabs/wayland616
- Category
- Design
- Updated
- 4d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Apply Conversational Proof to any claim: claim → evidence → reason → move-on pattern, with a library of 5 proof types (Anecdote, Receipt, Drive-By, Namecheck, Because). Outputs proof-blocks woven through copy, never an isolated proof section. Use when a draft makes claims that need to be believed and you want proof that reads like conversation, not a credentials wall. Not for designing testimonial graphics (use convert-proof-stack) and not for sourcing testimonials (that's a research task, not a copy task).
Convert Proof - Conversational Proof
"Proof in Donahoe copy never announces itself. It doesn't feel like 'evidence.' It feels like conversation - like you're just telling them what happened, what you saw, what the numbers said." - The Donahoe Method, Framework 2
This skill turns claims into believable, conversational proof using the four-step pattern (claim → evidence → reason → move on) and the five-type proof library (Anecdote, Receipt, Drive-By, Namecheck, Because).
The output is proof woven through copy - not a "proof section" with a logo bar.
When to Use
Trigger phrases: "add proof to this", "conversational proof", "donahoe proof", "prove this claim", "back this up", "testimonial as conversation", "drop the receipts", "skin the claim", /convert proof <claim or section>.
Use whenever copy contains a claim that needs to be believed but currently reads as assertion. Works at any granularity - a single sentence, a single bullet, a section, or a full draft.
Do NOT use for:
- Designing the visual proof layout (logo bars, video grids, stat blocks) - that's
convert-proof-stack - Sourcing testimonials from customers (research task, not copy task)
- Auditing existing proof for Method-fit (use
convert-audit) - Generating bullets from scratch (use
convert-bullets- though they import proof patterns)
Inputs
Required:
- The claim(s) - what does the copy assert that needs to be believed? "This system generates leads while you sleep." / "Most copywriting courses are wasting your time." / "I made $14k in 11 days." Each claim becomes a proof unit.
- Available evidence - anecdotes (real customer stories), receipts (numbers, dates, screenshots), credentials (resume items the seller has), names (people willing to be quoted), mechanisms (the why behind the result).
