email-promo
Skill32 starsChanged 8 months agoMITView on GitHub
Generate RMBC-structured promotional email copy with A/B subject line variants — short-form, high-impact direct response emails.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Zenobia0000/dtc-copywriting-skillsedited, first seen Mar 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- Zenobia0000/dtc-copywriting-skills★ 454% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository41 other files it gives its agents.
- ab-test-planSkill
- ad-angle-generatorSkill
- ad-creative-auditSkill
- advertorial-writerSkill
- bonus-stackSkill
- broadcast-emailSkill
- cart-abandonment-flowSkill
- checkout-abandonmentSkill
- competitor-offer-analysisSkill
- copy-rewriteSkill
- creative-briefSkill
- email-retention-sequencesSkill
- fb-ad-copySkill
- free-offer-briefSkill
- funnel-architectureSkill
- funnel-auditSkill
- guarantee-writerSkill
- hook-batterySkill
- ingredient-researchSkill
- lander-copySkill
- lead-writerSkill
- mechanism-ideationSkill
- media-buying-briefSkill
- offer-stackSkill
- order-form-croSkill
- pdp-ecomm-templateSkill
- post-purchase-sequenceSkill
- pricing-strategySkill
- reengagement-sequenceSkill
- rmbc-contextSkill
- rmbc-copy-auditSkill
- scarcity-urgencySkill
- soap-opera-sequenceSkill
- thank-you-pageSkill
- ugc-briefSkill
- unified-research-synthesizerSkill
- upsell-scriptSkill
- upsell-sequence-writerSkill
- vsl-scriptSkill
- webinar-registration-copySkill
- welcome-sequenceSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 8 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
Read rmbc-context/SKILL.md to load RMBC framework definitions.
- Distinctive: line 52
No ALL CAPS words
- Distinctive: line 53
No spam triggers (FREE!!!, Act Now, Limited Time)
- Distinctive: line 59
Must complement (not repeat) the subject line
- Distinctive: line 76
No images in the copy output (images reduce deliverability in cold-ish lists)
- Distinctive: line 80
If this email is part of a sequence, note:
- Distinctive: line 141
Specificity gate: Every claim in the copy must include a number, name, or timeframe — no "get results" or "improve your business"
- Distinctive: line 142
Mechanism quantification: When referencing the mechanism, include at least one specific data point (number, timeframe, study reference)
- Distinctive: line 144
Proof diversity: Use at least 2 different proof types (testimonial, statistical, authority, case study) — do not rely on a single proof mode
- Very specific: line 149
Run /hook-battery for subject line inspiration
- Very specific: line 150
Run /mechanism-ideation for mechanism tease content
- Very specific: line 152
Use /lead-writer for opening line variations
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
email-promo
Purpose
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.
Inputs
| 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) |
Execution Protocol
Step 1 — Load Framework Context
Read rmbc-context/SKILL.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.
Step 2 — Define Email Structure by Type
| 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 |
Step 3 — Write Subject Lines (3 Variants)
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:
- Max 50 characters (mobile truncation)
- No ALL CAPS words
- No spam triggers (FREE!!!, Act Now, Limited Time)
- Each must work without preview text context
Step 4 — Write Preview Text
- 40-90 characters
- Must complement (not repeat) the subject line
- Extends the curiosity loop or adds a proof point
- Appears in inbox preview on mobile — treat as a second headline
Step 5 — Write Email Body
Structure for all types:
- Opening line (1-2 sentences) — Hook that justifies the open. Deliver on the subject line promise immediately.
- Body (varies by type) — Deploy the email-type structure from Step 2. One idea per paragraph. Short paragraphs (1-3 sentences max).
- CTA (1 clear link/button) — One action. One link. Repeat it 2x in the email (mid-body and end).
- PS line — The most-read line after the subject. Use it for: guarantee restatement, deadline reminder, or strongest proof point.
Formatting rules:
- Short paragraphs: 1-3 sentences max
- Line breaks between every paragraph
- Bold key phrases sparingly (1-2 per email)
- One link/CTA — never split attention across multiple offers
- No images in the copy output (images reduce deliverability in cold-ish lists)
Step 6 — Write Sequence Context (if applicable)
If this email is part of a sequence, note:
- What email comes before this (what has the reader already seen?)
- What email comes after (what should this email set up?)
- Suggested send timing relative to previous email
Output Format
## 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]Quality Criteria
- 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)
Related Skills
- Run
/hook-batteryfor subject line inspiration - Run
/mechanism-ideationfor mechanism tease content - Drive email clicks to pages built with
/lander-copy - Use
/lead-writerfor opening line variations - Validate with
/rmbc-copy-audit
Attribution
Generated using RMBC framework by Stefan Georgi. Learn more: copyaccelerator.com/join
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

