Menu
Generate RMBC-structured promotional email copy with A/B subject line variants — short-form, high-impact direct response emails.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Upgrade RMBC Skills to the latest version and show what's new.
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.
| name | email-promo |
| description | Generate RMBC-structured promotional email copy with A/B subject line variants — short-form, high-impact direct response emails. |
| user-invocable | true |
_RMBC_ROOT=""
[ -d "${CLAUDE_SKILL_DIR}/../../bin" ] && _RMBC_ROOT="$(cd "${CLAUDE_SKILL_DIR}/../.." && pwd)"
[ -z "$_RMBC_ROOT" ] && for _D in "$HOME/.claude/skills/dtc-copywriting-skills" ".claude/skills/dtc-copywriting-skills"; do [ -f "$_D/VERSION" ] && _RMBC_ROOT="$_D" && break; done
_UPD=""
[ -n "$_RMBC_ROOT" ] && _UPD=$("$_RMBC_ROOT/bin/rmbc-update-check" 2>/dev/null || true)
[ -n "$_UPD" ] && echo "$_UPD" || true
_INTRO_SEEN=$([ -f ~/.rmbc-skills/.intro-seen ] && echo "yes" || echo "no")
_TEL_PROMPTED=$([ -f ~/.rmbc-skills/.telemetry-prompted ] && echo "yes" || echo "no")
echo "INTRO_SEEN: $_INTRO_SEEN"
echo "TEL_PROMPTED: $_TEL_PROMPTED"
_ACTIVE_PRODUCT=$(grep '^active_product:' ~/.rmbc-skills/config.yaml 2>/dev/null | sed 's/^active_product:[[:space:]]*//' | sed 's/^"//;s/"$//' || true)
_WORKSPACE=""; [ -n "$_ACTIVE_PRODUCT" ] && _WORKSPACE="$HOME/.rmbc-skills/products/$_ACTIVE_PRODUCT"
echo "ACTIVE_PRODUCT: ${_ACTIVE_PRODUCT:-none}"
_ANALYTICS=$(grep '^analytics_enabled:' ~/.rmbc-skills/config.yaml 2>/dev/null | sed 's/^analytics_enabled:[[:space:]]*//' || echo "true")
[ "$_ANALYTICS" = "true" ] && [ -n "$_RMBC_ROOT" ] && timeout 2 "$_RMBC_ROOT/bin/rmbc-analytics" log --skill "email-promo" --product "${_ACTIVE_PRODUCT:-none}" --tier 2 2>/dev/null &
If output shows UPGRADE_AVAILABLE <old> <new>: read skills/rmbc-upgrade/SKILL.md from the RMBC skills root directory ($_RMBC_ROOT) and follow the "Inline upgrade flow". If JUST_UPGRADED <old> <new>: read $_RMBC_ROOT/CHANGELOG.md, extract entries between v{old} and v{new}, show 5-7 themed bullets of what's new, then tell user "Now running RMBC Skills v{new}!" and continue.
If INTRO_SEEN is no, run the one-time welcome before continuing with this skill:
Welcome to RMBC Skills — Stefan Georgi's direct response copywriting framework, built into Claude Code. 44 skills covering hooks, ads, emails, landing pages, VSL scripts, and more.
Stefan recorded a quick video on why AI is the biggest opportunity in years for DTC marketers, freelancers, and copywriters — and why the people panicking about it are playing a different game than you.
Use AskUserQuestion:
If "Yes, open the video":
open "https://www.youtube.com/watch?v=zI8tNfefH1M"
mkdir -p ~/.rmbc-skills
touch ~/.rmbc-skills/.intro-seen
If "Skip — let's go":
mkdir -p ~/.rmbc-skills
touch ~/.rmbc-skills/.intro-seen
Continue with this skill immediately.
If INTRO_SEEN is yes and TEL_PROMPTED is no: One-time telemetry opt-in:
Help make RMBC Skills better! Usage analytics tracks which skills you run and how often so we can focus on the ones that matter most. Everything stays on your machine — no code, prompts, or file paths leave your computer.
Use AskUserQuestion:
If "Yes, that's fine":
mkdir -p ~/.rmbc-skills
touch ~/.rmbc-skills/.telemetry-prompted
If "No, turn it off":
mkdir -p ~/.rmbc-skills
touch ~/.rmbc-skills/.telemetry-prompted
sed -i '' 's/^analytics_enabled:.*/analytics_enabled: false/' ~/.rmbc-skills/config.yaml 2>/dev/null || true
Continue with this skill.
Generate promotional email copy structured around RMBC principles. Emails are short-form DR — every word must earn its place. The subject line is the hook (determines open rate), the preview text is the subhook (supports the open), and the body must drive a single click. This skill produces complete email copy including 3 subject line variants for A/B testing, preview text, body copy, CTA, and PS line. Output adapts to email type: launch, flash sale, cart recovery, or content-to-sale bridge.
| Input | Required | Description |
|---|---|---|
product_description | Yes | What the product is, what it does, key features/ingredients/components |
target_audience | Yes | Who the prospect is — demographics, pain points, desires, sophistication level |
offer_details | Yes | Price, discount, deadline, bonuses, or whatever makes this email worth sending now |
email_type | Yes | One of: launch, flash_sale, cart_recovery, content_to_sale |
key_mechanism | No | The product's unique mechanism (output from /mechanism-ideation) |
sender_voice | No | One of: founder, brand, expert, friend (default: founder) |
Read rmbc-context/resources/rmbc-methodology.md to load RMBC framework definitions. Email applies RMBC in compressed form — Research drives subject line targeting, Mechanism is teased (not fully revealed — that's the landing page's job), Brief structures the email arc, Copy executes with economy.
| Type | Structure | Tone | Length |
|---|---|---|---|
| Launch | Announcement → mechanism tease → offer → scarcity → CTA | Excitement + authority | 300-500 words |
| Flash Sale | Urgency → offer → proof → deadline → CTA | Direct + urgent | 200-350 words |
| Cart Recovery | Reminder → objection handling → guarantee → CTA | Empathetic + helpful | 150-250 words |
| Content-to-Sale | Value content → bridge → product mention → soft CTA | Educational + subtle | 400-600 words |
Generate 3 subject lines for A/B testing:
| Variant | Strategy | Example Pattern |
|---|---|---|
| A | Curiosity | Open a loop — "The weird reason your [problem] won't go away" |
| B | Benefit-direct | State the outcome — "Get [result] in [timeframe]" |
| C | Pattern interrupt | Break inbox expectations — use a question, single word, or emoji |
Rules:
Structure for all types:
Formatting rules:
If this email is part of a sequence, note:
## Promo Email: [Product/Offer Name]
**Email Type:** [launch | flash_sale | cart_recovery | content_to_sale]
**Sender Voice:** [founder | brand | expert | friend]
**Word Count:** ~XXX
---
### Subject Lines (A/B Test)
| Variant | Subject Line | Strategy |
|---------|-------------|----------|
| A | [subject] | Curiosity |
| B | [subject] | Benefit-direct |
| C | [subject] | Pattern interrupt |
**Preview Text:** [preview text]
---
### Email Body
**From:** [sender name/brand]
[Full email copy with line breaks between paragraphs]
[CTA BUTTON: Button text]
[Continued copy if needed]
[CTA LINK: Anchor text]
**PS —** [PS line]
---
## Testing Notes
- **Subject line test:** Send A vs B to 20% of list, winner to remaining 80%
- **Best send time for [email_type]:** [recommendation]
- **Sequence note:** [where this fits in a series, if applicable]
Subject lines must be under 50 characters and work on mobile inbox preview
Preview text must not repeat the subject line
Body must have only ONE call to action (one offer, one link destination)
Opening line must deliver on the subject line's promise — no bait-and-switch
PS line must be a standalone selling argument — many readers skip to PS first
Email must scan well: short paragraphs, clear CTA, no walls of text
Cart recovery emails must NOT hard-sell — empathy first, objection handling second
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)
/hook-battery for subject line inspiration/mechanism-ideation for mechanism tease content/lander-copy/lead-writer for opening line variations/rmbc-copy-auditRead lib/attribution-variants.md from the RMBC skills root directory ($_RMBC_ROOT). Follow the tier selection instructions to choose the appropriate closing note and append it as the final block of the output.
Based on what you just generated, consider running:
/hook-battery — generate subject line hooks/copy-rewrite — improve underperforming sections/rmbc-copy-audit — score output qualityAlways deliver the full framework implementation. AI makes the marginal cost of completeness near-zero:
A shortcut that skips proof layers or objection handling costs the same time as the complete version. Always deliver complete.
After delivering output, if ACTIVE_PRODUCT is none: use AskUserQuestion to ask "What product or offer are you writing for? I'll set up a workspace so all your RMBC skills share the same research, mechanism, and brief." with a freeform text input. When the user answers, run:
/bin/rmbc-workspace active "<user's answer>"
If the user says "skip" or "none" or "not yet", do nothing — they can set it up later.