메뉴
Generate risk-reversal guarantees that convert fence-sitters — money-back, conditional, better-than-money-back, double-your-money, and performance-based with headline, terms, and visual treatment using RMBC principles.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Generate structured A/B test plans for DTC funnels — hypothesis, control vs variant, primary metric, sample size estimate, test duration, and success criteria using RMBC principles.
Generate 5-7 unique ad angles for paid media campaigns — each a full strategic positioning direction with headline, body, visual, and platform fit.
Audit paid media ad creative (copy + visual direction) against RMBC and DR principles — score hook, mechanism, proof, CTA, and visual-copy alignment with actionable fixes.
Generate RMBC-structured advertorial and native ad copy that reads like editorial content but drives direct response conversions.
Design bonus stacks that increase perceived value without increasing fulfillment cost — 3-5 bonuses with name, description, perceived value, actual cost, and core offer complement rationale using RMBC principles.
Generate one-off broadcast emails for list engagement — content, story, controversy, case study, or flash promo types with 3 subject line options using RMBC principles.
| name | guarantee-writer |
| description | Generate risk-reversal guarantees that convert fence-sitters — money-back, conditional, better-than-money-back, double-your-money, and performance-based with headline, terms, and visual treatment using RMBC principles. |
| model | sonnet |
| user-invocable | true |
Generate risk-reversal guarantees that convert fence-sitters into buyers. The guarantee is the most underrated conversion element in direct response — it doesn't just reduce risk, it demonstrates confidence in your mechanism. A strong guarantee says "we believe in our [mechanism] so much that we'll put our money where our mouth is." This skill produces 3 guarantee options across different types, each with a headline, terms, visual treatment suggestion, and copy ready for the checkout page, sales page, and email.
| Input | Required | Description |
|---|---|---|
product_name | Yes | Product name and brief description of what it delivers |
price_point | Yes | Price — affects guarantee framing (higher price = stronger guarantee needed) |
guarantee_type | Yes | One of: money_back, conditional, better_than_money_back, double_money_back, performance_based, or all to generate one of each |
guarantee_duration | Yes | How long the guarantee lasts: 30, 60, 90, 365 days, or lifetime |
target_audience | Yes | Who the buyer is — their risk tolerance, sophistication, past experiences with guarantees |
Read rmbc-context/SKILL.md to load RMBC framework definitions. The guarantee is a Mechanism expression — it proves you believe in your own "why it works" story. Research reveals what risks the audience fears most. The Brief determines how aggressively to position the guarantee. Copy executes the guarantee language to feel confident, not defensive.
Before writing, understand what's actually at stake for the buyer:
| Risk Type | Question | Impact on Guarantee |
|---|---|---|
| Financial | Can they afford to lose this money? | Higher price = longer duration, stronger terms |
| Results | Do they believe the product will work? | Results skepticism = conditional or performance guarantee |
| Trust | Do they trust the company to honor the guarantee? | Low trust = simple process, no fine print, well-known payment processor |
| Effort | Will they have to work hard to get a refund? | Friction fear = "no questions asked" + clear process |
| Social | Will they feel foolish if it doesn't work? | Ego risk = frame guarantee as "smart insurance" not "safety net" |
For each requested type (or all 5 if all selected):
The standard. Simple, clear, no conditions.
Refund if the buyer follows the program/uses the product AND doesn't get results.
Buyer keeps something valuable AND gets a full refund.
If it doesn't work, buyer gets 2x their purchase price refunded.
Tied to a specific, measurable result.
For each guarantee, produce three versions:
Sales Page Version (3-5 sentences): Full guarantee with headline, named guarantee, terms, and process.
Checkout Version (1-2 sentences): Compressed guarantee placed near the payment button. Must build confidence in minimal space.
Email Version (2-3 sentences): Guarantee copy for follow-up emails to non-buyers. Emphasize the risk-free nature of trying.
For each guarantee, suggest:
## Guarantee Options: [Product Name]
**Price:** [price]
**Duration:** [duration]
**Audience Risk Profile:** [1-line summary of primary risk type]
---
### OPTION 1: [Guarantee Name] ([Type])
**Headline:** "[Guarantee headline]"
**Sales Page Copy:**
[3-5 sentence guarantee copy]
**Checkout Copy:**
[1-2 sentence compressed version]
**Email Copy:**
[2-3 sentence version for follow-up emails]
**Visual Treatment:**
- Badge: [shape, color, text]
- Placement: [where on page]
- Typography: [what to emphasize]
**Conversion impact:** [expected effect on conversion and refund rate]
---
### OPTION 2: [Same format]
---
### OPTION 3: [Same format]
---
### RECOMMENDATION
**Best option for this product:** [Option #] because [reason tied to audience risk profile and price point].
**Test against:** [Option #] — run as A/B test to validate.
Every guarantee must have a name — unnamed guarantees feel generic and forgettable
Terms must be specific about duration, process, and any conditions — ambiguity feels like a loophole to buyers
The refund process must be described in one sentence — complex processes signal the company doesn't want to honor it
Checkout version must work in 1-2 sentences — the buyer is at the payment button, not reading paragraphs
Conditional guarantees must name specific, achievable conditions — unreasonable conditions feel like a trap
Double-money-back guarantees must only be recommended for proven products with low refund history
Visual treatment must specify placement near the CTA — a guarantee buried in the footer doesn't reduce risk
Specificity gate: Every claim in the copy must include a number, name, or timeframe — no "get results" or "improve your business"
Mechanism quantification: When referencing the mechanism, include at least one specific data point (number, timeframe, study reference)
Audience journey: The copy must reference where the reader IS (what they've tried, what's failing) — not just who they are demographically
Proof diversity: Use at least 2 different proof types (testimonial, statistical, authority, case study) — do not rely on a single proof mode
Objection handling: The copy must address at least 2 likely objections with concrete responses (ROI math, proof of similar result, risk reversal)
/offer-stack to integrate the guarantee into the full offer architecture/order-form-cro to place the guarantee optimally on the checkout page/lander-copy for the sales page that presents the guarantee/ab-test-plan to test guarantee variations against each other/checkout-abandonment to diagnose if weak guarantee copy is causing drop-off/rmbc-copy-auditGenerated using RMBC framework by Stefan Georgi. Learn more: copyaccelerator.com/join