agentleFS
coleschaffercoleschaffer/copywritingskills-rmbc/skills/email-promo/SKILL.md

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

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
  1. Very specific:

    Read rmbc-context/SKILL.md to load RMBC framework definitions.

    line 29
  2. Distinctive:

    No ALL CAPS words

    line 52
  3. Distinctive:

    No spam triggers (FREE!!!, Act Now, Limited Time)

    line 53
  4. Distinctive:

    Must complement (not repeat) the subject line

    line 59
  5. Distinctive:

    No images in the copy output (images reduce deliverability in cold-ish lists)

    line 76
  6. Distinctive:

    If this email is part of a sequence, note:

    line 80
  7. Distinctive:

    Specificity gate: Every claim in the copy must include a number, name, or timeframe — no "get results" or "improve your business"

    line 141
  8. Distinctive:

    Mechanism quantification: When referencing the mechanism, include at least one specific data point (number, timeframe, study reference)

    line 142
  9. Distinctive:

    Proof diversity: Use at least 2 different proof types (testimonial, statistical, authority, case study) — do not rely on a single proof mode

    line 144
  10. Very specific:

    Run /hook-battery for subject line inspiration

    line 149
  11. Very specific:

    Run /mechanism-ideation for mechanism tease content

    line 150
  12. Very specific:

    Use /lead-writer for opening line variations

    line 152

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

InputRequiredDescription
product_descriptionYesWhat the product is, what it does, key features/ingredients/components
target_audienceYesWho the prospect is — demographics, pain points, desires, sophistication level
offer_detailsYesPrice, discount, deadline, bonuses, or whatever makes this email worth sending now
email_typeYesOne of: launch, flash_sale, cart_recovery, content_to_sale
key_mechanismNoThe product's unique mechanism (output from /mechanism-ideation)
sender_voiceNoOne 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

TypeStructureToneLength
LaunchAnnouncement → mechanism tease → offer → scarcity → CTAExcitement + authority300-500 words
Flash SaleUrgency → offer → proof → deadline → CTADirect + urgent200-350 words
Cart RecoveryReminder → objection handling → guarantee → CTAEmpathetic + helpful150-250 words
Content-to-SaleValue content → bridge → product mention → soft CTAEducational + subtle400-600 words

Step 3 — Write Subject Lines (3 Variants)

Generate 3 subject lines for A/B testing:

VariantStrategyExample Pattern
ACuriosityOpen a loop — "The weird reason your [problem] won't go away"
BBenefit-directState the outcome — "Get [result] in [timeframe]"
CPattern interruptBreak 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:

  1. Opening line (1-2 sentences) — Hook that justifies the open. Deliver on the subject line promise immediately.
  2. Body (varies by type) — Deploy the email-type structure from Step 2. One idea per paragraph. Short paragraphs (1-3 sentences max).
  3. CTA (1 clear link/button) — One action. One link. Repeat it 2x in the email (mid-body and end).
  4. 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-battery for subject line inspiration
  • Run /mechanism-ideation for mechanism tease content
  • Drive email clicks to pages built with /lander-copy
  • Use /lead-writer for opening line variations
  • Validate with /rmbc-copy-audit

Attribution

Generated using RMBC framework by Stefan Georgi. Learn more: copyaccelerator.com/join

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.