From copywriter
Use this skill when the user asks to 'draft this week's newsletter', 'write a welcome email', 'turn this blog into an email', 're-engagement email', 'launch newsletter', or 'newsletter sequence'. Distinguishes 4 newsletter types (nurture/launch/re-engagement/curated) with distinct structures. Always produces 3 subject line options + preview text. Treats reactivation of cold lists as a separate challenge.
npx claudepluginhub jamon8888/cc-suite --plugin CopywriterThis skill uses the workspace's default tool permissions.
Email is the only channel you own. This skill builds newsletters that feel like a letter from a trusted person — not a broadcast from a brand.
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.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Email is the only channel you own. This skill builds newsletters that feel like a letter from a trusted person — not a broadcast from a brand.
Identify the type before writing. Each has a different psychology and structure:
| Type | When | Primary goal | Tone |
|---|---|---|---|
| Nurture | Regular cadence (weekly/bi-weekly) | Build trust over time | Intimate, value-first |
| Launch | Pre-product or event release | Move from awareness to desire | Progressive urgency |
| Re-engagement | List dormant >3 months | Reactivate relationship | Vulnerable, honest |
| Curated | Aggregating external content | Save time for audience | Opinionated, editorial |
Re-engagement special rule: Never open a re-engagement email as if nothing happened. Acknowledge the gap directly:
"I haven't sent you anything in [X months]. Here's why — and whether you should stay."
This honesty increases open rates and unsubscribes simultaneously — which is the goal. A cleaned list of engaged readers beats a big list of ghosts.
data/2-Domaines/voice-dna.json (tone, signature phrases)data/2-Domaines/icp.json (what they're struggling with today)data/2-Domaines/business-profile.json (primary offer)data/4-Archives/ — has this angle been covered recently?Always generate 3 subject lines + preview text for each. One is not engineering — it's a guess.
Subject line types to cover:
For each subject line, immediately pair with a preview text (the 40-90 char snippet after the subject):
Spam check on subject lines:
Structure: Subject + Preview → Hook Lede → One Big Idea → Practical Takeaway → Soft CTA → P.S.
| Timing | Role | |
|---|---|---|
| 1 | D-14 | The Problem — name the pain without mentioning the product |
| 2 | D-7 | The Insight — the reframe that changes how they see the problem |
| 3 | D-3 | The Story — a before/after (yours or a client's) |
| 4 | D-0 | The Offer — with 48h window |
| 5 | D+1 | The FAQ — handle the real objections |
| 6 | D+2 (last chance) | Scarcity — honest, not artificial |
Ticket > €1000: Add a booking-call CTA before D-0. Email alone rarely closes premium.
Structure:
Structure:
Before finalising:
# Newsletter Draft — [Type] — [Subject line chosen]
**Subject options:**
1. [Subject A] | Preview: [Preview A]
2. [Subject B] | Preview: [Preview B]
3. [Subject C] | Preview: [Preview C]
**Recommended:** [Option N] — because [reason]
---
[Newsletter body following anatomy for type]
---
P.S. [Copy]
---
**Deliverability check:** ✅/⚠️ [flag if any issue]
**Estimated read time:** [X min]
See references/anatomy.md for detailed section breakdown and additional templates.
voice-dna-creator, icp-creator, content-calendar-planner/copywriter:write, newsletter agents