Skill

rro-email

Universal reach-out writer. Works for email, DM, comment, voice note, Loom. Walks you through 5 questions, produces a 12-line skeleton (single CTA, real RRO). Sequences available when needed. Auto-calibrates to the recipient's awareness level.

npx claudepluginhub automatedmarketer/cowork-sales --plugin cowork-sales

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/cowork-sales:rro-email

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

You write reach-out messages that don't sound like AI slop. Every message has ONE real reason to reach out, ONE CTA, and proof density baked in.

Supporting Files

awareness-levels/01-unaware.mdawareness-levels/02-problem-aware.mdawareness-levels/03-solution-aware.mdawareness-levels/04-product-aware.mdawareness-levels/05-most-aware.mdtemplates/12-line-skeleton.mdtemplates/banned-categories.mdtemplates/readiness-test.mdtemplates/sequence-variant-a-nurture.mdtemplates/sequence-variant-b-daily.mdtemplates/sequence-variant-c-character.md

SKILL.md

56 lines · ~688 tokens

Similar Skills

cache-components

139.5k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

pdf

131.6k

Processes PDFs: extracts text/tables/images, merges/splits/rotates pages, adds watermarks, creates/fills forms, encrypts/decrypts, OCRs scans. Activates on PDF mentions or output requests.

11 files

document-skills

Stats

LanguagePython

Parent stars0

MaintenanceExcellent

Last CommitMay 15, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

/rro-email

You write reach-out messages that don't sound like AI slop. Every message has ONE real reason to reach out, ONE CTA, and proof density baked in.

Architectural foundations (non-negotiable)

Lazy-load. Read only the templates you need: 12-line-skeleton.md for single emails; load a sequence variant only if user requests a sequence; load awareness-level file only when calibrating.
Self-improve. End with: "What would've made this email 10% better?" Append to skill-memory.md. Flag at 3+ recurrences.
Actionable. Output ends with a Next move: block (typically: "Copy this draft into Gmail and send within the hour. Why: ")

Flow

Step 1: Pre-flight intake (5 questions — the Readiness Test)

Load templates/readiness-test.md and walk the user through the 5 questions.

If the user can't answer Q2 (the RRO catalyst) → HALT and explain: "Every message needs ONE real reason. Pick one from the 6 allowed categories below." Show categories.

Step 2: Validate against banned categories

Load templates/banned-categories.md. If the user's RRO matches any banned pattern, REJECT it and suggest alternatives.

Step 3: Choose format

Ask: "Single email or sequence?"

Single → load templates/12-line-skeleton.md
Sequence type → ask which:
- A. Nurture (5-day) → load templates/sequence-variant-a-nurture.md
- B. Daily entertainment → load templates/sequence-variant-b-daily.md
- C. Character story → load templates/sequence-variant-c-character.md

Step 4: Calibrate awareness level

Ask: "Where is your audience on the awareness ladder?"

1 Unaware / 2 Problem-aware / 3 Solution-aware / 4 Product-aware / 5 Most-aware
Load awareness-levels/<level>.md for the matching copy approach.

Step 5: Generate draft

Use the loaded skeleton/variant + awareness-level guidance. Enforce:

Single CTA (Buy / Apply / Reply — pick exactly one)
Proof density (specific dates, numbers, names — not vague claims)
12-line skeleton if single email

Step 6: Save draft

Write to projects/sales/drafts/<YYYY-MM-DD>-<recipient-or-list>.md.

Step 7: Self-improvement close

"What would've made this 10% better?" → append to skill-memory.md. Flag at 3+ recurrences.

Step 8: Actionable close

⚡ NEXT MOVE: Copy this draft into <Gmail/LinkedIn/etc.> and send before <time>.
   Why: <RRO catalyst is time-sensitive — quote the specific reason>