email-write

Name: email-write
Author: AgriciDaniel

58installs26forks

How to install email-write?

agricidaniel/claude-email/email-write

$npx -y skills add AgriciDaniel/claude-email --skill email-write

Installs into the current project.

Summary

Compose high-converting emails using proven copy frameworks (PAS, AIDA, BAB, FAB, 4Ps). Generates subject line variants with scores, responsive HTML templates with dark mode support, plain-text fallback, and preheader recommendations. Optimized for cold outreach, newsletters, pro

Files · 1

View on GitHub

SKILL.md

1	# Email Write Sub-Skill
2
3	## Purpose
4
5	Generate professional, high-converting email copy using proven copywriting frameworks. Produces subject line variants with scoring, responsive HTML templates with dark mode support, plain-text fallback, and preheader recommendations.
6
7	## Activation
8
9	This sub-skill is invoked by the main `/email` skill when the user needs to compose a new email.
10
11	## Workflow
12
13	### 1. Gather Context
14
15	First, check if `email-profile.md` exists in the project directory. If yes, load business type, tone preferences, and target audience from the profile.
16
17	If no profile exists or user provides new context, ask for:
18
19	- Email Purpose: cold outreach, newsletter, product launch, promotional, re-engagement, welcome, feature announcement, etc.
20	- Recipient: name, role, relationship (new lead, existing customer, subscriber, team member)
21	- Tone: professional, friendly, casual, authoritative, empathetic, enthusiastic
22	- Business Type: (from profile or ask) SaaS, e-commerce, service business, agency, creator, B2B, B2C
23	- Key Message: what action should the recipient take?
24	- Additional Context: product details, promotion details, deadline, personalization data
25
26	### 2. Select Copy Framework
27
28	Based on the email purpose, choose the appropriate framework from `references/copy-frameworks.md`:
29
30	\| Email Purpose \| Recommended Framework \| Why \|
31	\|--------------\|----------------------\|-----\|
32	\| Cold outreach \| PAS \| Empathy-driven, addresses pain points \|
33	\| Product launch \| AIDA \| Builds excitement, drives action \|
34	\| Newsletter \| BAB or AIDA \| Aspirational or engaging storytelling \|
35	\| Feature announcement \| FAB \| Clear value proposition for features \|
36	\| Promotional/sale \| AIDA \| Creates desire and urgency \|
37	\| Re-engagement \| PAS \| Identifies problem of disengagement \|
38	\| Welcome email \| BAB \| Shows transformation journey \|
39	\| Case study \| 4Ps \| Proof-heavy, testimonial-driven \|
40	\| Review request \| PAS \| Empathetic ask for feedback \|
41	\| Appointment reminder \| Direct \| No framework needed \|
42
43	If uncertain, default to AIDA for marketing emails or PAS for relationship emails.
44
45	### 3. Generate Subject Lines
46
47	Create 3 subject line variants using these strategies:
48
49	1. Curiosity-Driven: Creates intrigue, open loop, question, teaser
50	2. Benefit-Driven: Clear value proposition, outcome, result
51	3. Urgency-Driven: Time-sensitive, scarcity, FOMO (but not spammy)
52
53	Subject Line Rules:
54	- Optimal length: 6-10 words / 30-50 characters
55	- Never use ALL CAPS
56	- Maximum 1 exclamation mark per subject line
57	- Avoid spam triggers: "FREE!!!", "Act Now", "Limited Time Only", "Guaranteed", "Cash", "No obligation"
58	- Include personalization where possible (beyond first name: behavior, location, purchase history)
59	- Use power words: exclusive, secret, insider, proven, breakthrough, transform, discover
60
61	Scoring Methodology (0-100):
62
63	\| Criteria \| Weight \| Scoring \|
64	\|----------\|--------\|---------\|
65	\| Length \| 20 \| 100 if 30-50 chars, -10 per 5 chars over/under \|
66	\| Power Words \| 20 \| +20 per power word (max 2) \|
67	\| Personalization \| 25 \| +25 if personalized beyond first name \|
68	\| Spam Triggers \| -50 \| -50 if contains spam word \|
69	\| Clarity \| 20 \| 100 if benefit/topic is clear \|
70	\| Curiosity \| 15 \| +15 if creates open loop \|
71
72	Minimum passing score: 70
73
74	### 4. Write Preheader Text
75
76	Generate preheader recommendation (30-80 characters):
77
78	- Must complement (not repeat) the subject line
79	- Include secondary value proposition or CTA preview
80	- Avoid generic text like "View this email in your browser"
81
82	Example:
83	- Subject: "Your personalized SEO roadmap is ready"
84	- Preheader: "3 quick wins to boost your rankings this week"
85
86	### 5. Compose Email Body
87
88	Apply the chosen framework structure. Load full framework details from `references/copy-frameworks.md` before writing.
89
90	General Email Writing Rules:
91
92	- Opening: Hook in first sentence, address recipient by name if available
93	- Body: Use short paragraphs (2-3 sentences max), bullet points for scannability
94	- Tone: Match requested tone from profile or user input
95	- Personalization: Use merge tags like `{{firstName}}`, `{{company}}`, `{{productName}}`
96	- CTA: One primary CTA, clear and action-oriented ("Get Your Free Audit", "Claim Your Spot", "Start Your Trial")
97	- Social Proof: Include if available (testimonial, stat, case study result)
98	- Signature: Professional sign-off with name, title, company
99
100	Framework-Specific Structure:
101
102	Load the full structure from `refe

People who liked this also viewed

6 picks

Type

email-write

58installs26forks

View on GitHub

How to install email-write?

agricidaniel/claude-email/email-write

$npx -y skills add AgriciDaniel/claude-email --skill email-write

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Email Write Sub-Skill
2
3	## Purpose
4
5	Generate professional, high-converting email copy using proven copywriting frameworks. Produces subject line variants with scoring, responsive HTML templates with dark mode support, plain-text fallback, and preheader recommendations.
6
7	## Activation
8
9	This sub-skill is invoked by the main `/email` skill when the user needs to compose a new email.
10
11	## Workflow
12
13	### 1. Gather Context
14
15	First, check if `email-profile.md` exists in the project directory. If yes, load business type, tone preferences, and target audience from the profile.
16
17	If no profile exists or user provides new context, ask for:
18
19	- Email Purpose: cold outreach, newsletter, product launch, promotional, re-engagement, welcome, feature announcement, etc.
20	- Recipient: name, role, relationship (new lead, existing customer, subscriber, team member)
21	- Tone: professional, friendly, casual, authoritative, empathetic, enthusiastic
22	- Business Type: (from profile or ask) SaaS, e-commerce, service business, agency, creator, B2B, B2C
23	- Key Message: what action should the recipient take?
24	- Additional Context: product details, promotion details, deadline, personalization data
25
26	### 2. Select Copy Framework
27
28	Based on the email purpose, choose the appropriate framework from `references/copy-frameworks.md`:
29
30	\| Email Purpose \| Recommended Framework \| Why \|
31	\|--------------\|----------------------\|-----\|
32	\| Cold outreach \| PAS \| Empathy-driven, addresses pain points \|
33	\| Product launch \| AIDA \| Builds excitement, drives action \|
34	\| Newsletter \| BAB or AIDA \| Aspirational or engaging storytelling \|
35	\| Feature announcement \| FAB \| Clear value proposition for features \|
36	\| Promotional/sale \| AIDA \| Creates desire and urgency \|
37	\| Re-engagement \| PAS \| Identifies problem of disengagement \|
38	\| Welcome email \| BAB \| Shows transformation journey \|
39	\| Case study \| 4Ps \| Proof-heavy, testimonial-driven \|
40	\| Review request \| PAS \| Empathetic ask for feedback \|
41	\| Appointment reminder \| Direct \| No framework needed \|
42
43	If uncertain, default to AIDA for marketing emails or PAS for relationship emails.
44
45	### 3. Generate Subject Lines
46
47	Create 3 subject line variants using these strategies:
48
49	1. Curiosity-Driven: Creates intrigue, open loop, question, teaser
50	2. Benefit-Driven: Clear value proposition, outcome, result
51	3. Urgency-Driven: Time-sensitive, scarcity, FOMO (but not spammy)
52
53	Subject Line Rules:
54	- Optimal length: 6-10 words / 30-50 characters
55	- Never use ALL CAPS
56	- Maximum 1 exclamation mark per subject line
57	- Avoid spam triggers: "FREE!!!", "Act Now", "Limited Time Only", "Guaranteed", "Cash", "No obligation"
58	- Include personalization where possible (beyond first name: behavior, location, purchase history)
59	- Use power words: exclusive, secret, insider, proven, breakthrough, transform, discover
60
61	Scoring Methodology (0-100):
62
63	\| Criteria \| Weight \| Scoring \|
64	\|----------\|--------\|---------\|
65	\| Length \| 20 \| 100 if 30-50 chars, -10 per 5 chars over/under \|
66	\| Power Words \| 20 \| +20 per power word (max 2) \|
67	\| Personalization \| 25 \| +25 if personalized beyond first name \|
68	\| Spam Triggers \| -50 \| -50 if contains spam word \|
69	\| Clarity \| 20 \| 100 if benefit/topic is clear \|
70	\| Curiosity \| 15 \| +15 if creates open loop \|
71
72	Minimum passing score: 70
73
74	### 4. Write Preheader Text
75
76	Generate preheader recommendation (30-80 characters):
77
78	- Must complement (not repeat) the subject line
79	- Include secondary value proposition or CTA preview
80	- Avoid generic text like "View this email in your browser"
81
82	Example:
83	- Subject: "Your personalized SEO roadmap is ready"
84	- Preheader: "3 quick wins to boost your rankings this week"
85
86	### 5. Compose Email Body
87
88	Apply the chosen framework structure. Load full framework details from `references/copy-frameworks.md` before writing.
89
90	General Email Writing Rules:
91
92	- Opening: Hook in first sentence, address recipient by name if available
93	- Body: Use short paragraphs (2-3 sentences max), bullet points for scannability
94	- Tone: Match requested tone from profile or user input
95	- Personalization: Use merge tags like `{{firstName}}`, `{{company}}`, `{{productName}}`
96	- CTA: One primary CTA, clear and action-oriented ("Get Your Free Audit", "Claim Your Spot", "Start Your Trial")
97	- Social Proof: Include if available (testimonial, stat, case study result)
98	- Signature: Professional sign-off with name, title, company
99
100	Framework-Specific Structure:
101
102	Load the full structure from `refe

People who liked this also viewed

6 picks

Type