Claude Email Skill
Use Claude for structured reasoning and critique, but keep the message accountable to the brief, audience, and approval owner.
Decision Lens
- Primary lens: Claude-oriented email prompts, campaign drafting, critique loops, and human review.
- Common request signals: prompt packs, campaign draft evaluation, review rubrics, rewrite loops, and Claude Code email handoffs.
- Default posture: Use Claude for structured reasoning and critique, but keep the message accountable to the brief, audience, and approval owner.
- Useful output family: Claude prompts, campaign drafts, critique rubrics, rewrite instructions, variant sets, and approval-ready copy packets.
- Production boundary: separate recommendation from execution.
When To Use
Use this skill for Claude-oriented email prompts, campaign drafting, critique loops, and human review. It is designed for agent workflows where email work must be specific, reviewable, and safe across planning, drafting, implementation, QA, or operational handoff.
Operating Workflow
- Turn the request into a clear email brief with audience, promise, proof, CTA, tone, constraints, and forbidden claims.
- Choose the Claude task shape: ideation, first draft, critique, rewrite, variant generation, or final QA.
- Provide Claude with bounded source material and ask it to cite which input drove each major claim.
- Review outputs against a rubric instead of taste alone: relevance, specificity, risk, readability, and production readiness.
- For rewrites, preserve approved facts and change only the requested dimension such as tone, length, structure, or CTA emphasis.
- Mark anything that needs human approval, legal review, data validation, or ESP testing.
Review Criteria
- The prompt gives Claude enough context without exposing unnecessary private data.
- Drafts do not invent guarantees, customer proof, pricing, or compliance claims.
- Critique feedback is actionable and tied to the brief.
- Variants test a meaningful hypothesis rather than superficial wording.
- Final copy includes subject, preview, body, CTA, and QA notes when relevant.
Output Pattern
Return Claude prompts, campaign drafts, critique rubrics, rewrite instructions, variant sets, and approval-ready copy packets. Keep recommendations concrete. Separate analysis from live-system actions, and require explicit approval before sending email, importing contacts, changing DNS, altering suppression rules, or editing production automations.
1---2name: claudeemailskill3description: Use when Codex, Hermes, OpenClaw, Claude Code, Cowork, or another AI agent needs to plan, review, implement, audit, or improve email work focused on Claude-oriented email prompts, campaign drafting, critique loops, and human review. Triggers include requests about prompt packs, campaign draft evaluation, review rubrics, rewrite loops, and Claude Code email handoffs.4---5
6# Claude Email Skill
7
8Use Claude for structured reasoning and critique, but keep the message accountable to the brief, audience, and approval owner.
9
10## Decision Lens
11
12- Primary lens: Claude-oriented email prompts, campaign drafting, critique loops, and human review.
13- Common request signals: prompt packs, campaign draft evaluation, review rubrics, rewrite loops, and Claude Code email handoffs.
14- Default posture: Use Claude for structured reasoning and critique, but keep the message accountable to the brief, audience, and approval owner.
15- Useful output family: Claude prompts, campaign drafts, critique rubrics, rewrite instructions, variant sets, and approval-ready copy packets.
16- Production boundary: separate recommendation from execution.
17
18## When To Use
19
20Use this skill for Claude-oriented email prompts, campaign drafting, critique loops, and human review. It is designed for agent workflows where email work must be specific, reviewable, and safe across planning, drafting, implementation, QA, or operational handoff.
21
22## Operating Workflow
23
241. Turn the request into a clear email brief with audience, promise, proof, CTA, tone, constraints, and forbidden claims.
252. Choose the Claude task shape: ideation, first draft, critique, rewrite, variant generation, or final QA.
263. Provide Claude with bounded source material and ask it to cite which input drove each major claim.
274. Review outputs against a rubric instead of taste alone: relevance, specificity, risk, readability, and production readiness.
285. For rewrites, preserve approved facts and change only the requested dimension such as tone, length, structure, or CTA emphasis.
296. Mark anything that needs human approval, legal review, data validation, or ESP testing.
30
31## Review Criteria
32
33- The prompt gives Claude enough context without exposing unnecessary private data.
34- Drafts do not invent guarantees, customer proof, pricing, or compliance claims.
35- Critique feedback is actionable and tied to the brief.
36- Variants test a meaningful hypothesis rather than superficial wording.
37- Final copy includes subject, preview, body, CTA, and QA notes when relevant.
38
39## Output Pattern
40
41Return Claude prompts, campaign drafts, critique rubrics, rewrite instructions, variant sets, and approval-ready copy packets. Keep recommendations concrete. Separate analysis from live-system actions, and require explicit approval before sending email, importing contacts, changing DNS, altering suppression rules, or editing production automations.
aiskillstore