email-write — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited email-write (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
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.
This sub-skill is invoked by the main /email skill when the user needs to compose a new email.
First, check if email-profile.md exists in the project directory. If yes, load business type, tone preferences, and target audience from the profile.
If no profile exists or user provides new context, ask for:
Based on the email purpose, choose the appropriate framework from references/copy-frameworks.md:
| Email Purpose | Recommended Framework | Why |
|---|---|---|
| Cold outreach | PAS | Empathy-driven, addresses pain points |
| Product launch | AIDA | Builds excitement, drives action |
| Newsletter | BAB or AIDA | Aspirational or engaging storytelling |
| Feature announcement | FAB | Clear value proposition for features |
| Promotional/sale | AIDA | Creates desire and urgency |
| Re-engagement | PAS | Identifies problem of disengagement |
| Welcome email | BAB | Shows transformation journey |
| Case study | 4Ps | Proof-heavy, testimonial-driven |
| Review request | PAS | Empathetic ask for feedback |
| Appointment reminder | Direct | No framework needed |
If uncertain, default to AIDA for marketing emails or PAS for relationship emails.
Create 3 subject line variants using these strategies:
Subject Line Rules:
Scoring Methodology (0-100):
| Criteria | Weight | Scoring |
|---|---|---|
| Length | 20 | 100 if 30-50 chars, -10 per 5 chars over/under |
| Power Words | 20 | +20 per power word (max 2) |
| Personalization | 25 | +25 if personalized beyond first name |
| Spam Triggers | -50 | -50 if contains spam word |
| Clarity | 20 | 100 if benefit/topic is clear |
| Curiosity | 15 | +15 if creates open loop |
Minimum passing score: 70
Generate preheader recommendation (30-80 characters):
Example:
Apply the chosen framework structure. Load full framework details from references/copy-frameworks.md before writing.
General Email Writing Rules:
{{firstName}}, {{company}}, {{productName}}Framework-Specific Structure:
Load the full structure from references/copy-frameworks.md and apply. Each framework has:
Create a responsive, dark-mode compatible HTML email using these specifications:
HTML Template Structure:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="color-scheme" content="light dark">
<meta name="supported-color-schemes" content="light dark">
<title>{{emailSubject}}</title>
<style>
/* Inline critical CSS */
body { margin: 0; padding: 0; font-family: Arial, Helvetica, sans-serif; }
table { border-collapse: collapse; }
.email-container { max-width: 600px; margin: 0 auto; }
.body-text { font-size: 16px; line-height: 1.6; color: #333333; }
.cta-button {
display: inline-block;
padding: 14px 28px;
background-color: #0066cc;
color: #ffffff;
text-decoration: none;
border-radius: 4px;
font-weight: bold;
min-height: 44px;
min-width: 44px;
}
/* Dark mode styles */
@media (prefers-color-scheme: dark) {
body { background-color: #1a1a1a !important; }
.body-text { color: #e0e0e0 !important; }
.email-container { background-color: #2a2a2a !important; }
}
/* Mobile responsive */
@media only screen and (max-width: 600px) {
.body-text { font-size: 14px !important; }
.headline { font-size: 22px !important; }
.cta-button { display: block !important; width: 100% !important; }
}
</style>
</head>
<body>
<!-- Email content goes here -->
</body>
</html>HTML Rules:
<style> tags)color-scheme: light dark meta tag@media (prefers-color-scheme: dark)CTA Button Best Practices:
<a> tag with role="button" for accessibilityCreate a plain-text fallback with:
Present the final email composition in this structure:
## Email Composition
**Framework**: [chosen framework name]
**Purpose**: [email purpose]
**Tone**: [tone]
**Recipient Type**: [recipient type]
---
### Subject Line Options
| # | Subject | Score | Type | Notes |
|---|---------|-------|------|-------|
| 1 | [subject line 1] | 87 | Curiosity | [why this works] |
| 2 | [subject line 2] | 82 | Benefit | [why this works] |
| 3 | [subject line 3] | 79 | Urgency | [why this works] |
**Recommended**: #1 (highest score)
**Preheader Text**: [30-80 char preheader recommendation]
---
### Email Body (Plain Text)
[Full email body using framework structure]
[Include merge tags like {{firstName}}, {{company}}]
[CTA]
[Signature]
---
### HTML Version
[Complete HTML email code with inline CSS, dark mode support, responsive design]
---
### Plain Text Version
[Plain text fallback with line breaks, CTA as full URL]
---
### Email Metadata
- **Word Count**: [body word count]
- **Reading Time**: [estimated reading time]
- **Character Count** (with spaces): [count]
- **CTA Count**: [number of CTAs]
---
### Next Steps
- [ ] Review and edit copy
- [ ] Choose subject line variant
- [ ] Test HTML rendering in email client preview tool
- [ ] Send as draft via MCP (if available) or copy to email platform
- [ ] A/B test subject lines if sending to large listBefore delivering the email, verify:
If any gate fails, revise before output.
references/copy-frameworks.md is missing, warn user and use basic AIDA structureemail-profile.md is missing, prompt user for context (don't fail)references/copy-frameworks.md - Full framework structures and examplesemail-profile.md - User's business context and preferences (optional)User: "Write a cold outreach email to a SaaS founder about my SEO audit service"
Agent:
email-send sub-skill or MCP email tools~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.