Email Campaign Skill
Run the campaign as a controlled operation: brief, audience, creative, QA, launch, monitor, learn.
Decision Lens
- Primary lens: campaign briefs, audience logic, creative QA, launch readiness, and post-send analysis.
- Common request signals: campaign briefs, creative review, performance retrospectives, audience QA, launch checklists, and campaign optimization.
- Default posture: Run the campaign as a controlled operation: brief, audience, creative, QA, launch, monitor, learn.
- Useful output family: campaign briefs, audience QA tables, creative reviews, launch checklists, test plans, and post-send retrospectives.
- Production boundary: separate recommendation from execution.
- Evidence boundary: say which source material supports the recommendation.
- Review boundary: identify the human owner for risky changes.
- Data boundary: do not assume missing fields, consent, or suppression state.
- Platform boundary: describe provider-specific steps in operational language.
- Measurement boundary: define what success or recovery will look like.
- Handoff boundary: make the next step clear to another agent.
- Rollback boundary: name the safest way to undo live-system changes.
- Escalation boundary: stop when legal, compliance, DNS, or sending authority is unclear.
When To Use
Use this skill for campaign briefs, audience logic, creative QA, launch readiness, and post-send analysis. 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
- Start with the campaign brief: objective, audience, offer, send window, success metric, constraints, and approval owner.
- Validate audience logic before copy, including inclusions, exclusions, consent, suppression, and expected recipient count.
- Review creative for promise match across subject, preview, body, proof, CTA, landing page, and follow-up path.
- Prepare launch QA: links, tracking, personalization, rendering, plain-text fallback, footer, and reply handling.
- For analysis, compare performance against baseline, segment, source, and hypothesis rather than judging one metric alone.
- Return a launch decision or retrospective with next actions and risks.
Review Criteria
- The campaign has one primary goal and one primary CTA.
- Audience eligibility and exclusions are written in operational terms.
- The creative does not promise more than the landing page delivers.
- Post-send analysis includes deliverability and list-quality context.
- Recommendations separate immediate fixes from future tests.
Output Pattern
Return campaign briefs, audience QA tables, creative reviews, launch checklists, test plans, and post-send retrospectives. 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: emailcampaignskill3description: Use when Codex, Hermes, OpenClaw, Claude Code, Cowork, or another AI agent needs to plan, review, implement, audit, or improve email work focused on campaign briefs, audience logic, creative QA, launch readiness, and post-send analysis. Triggers include requests about campaign briefs, creative review, performance retrospectives, audience QA, launch checklists, and campaign optimization.4---5
6# Email Campaign Skill
7
8Run the campaign as a controlled operation: brief, audience, creative, QA, launch, monitor, learn.
9
10## Decision Lens
11
12- Primary lens: campaign briefs, audience logic, creative QA, launch readiness, and post-send analysis.
13- Common request signals: campaign briefs, creative review, performance retrospectives, audience QA, launch checklists, and campaign optimization.
14- Default posture: Run the campaign as a controlled operation: brief, audience, creative, QA, launch, monitor, learn.
15- Useful output family: campaign briefs, audience QA tables, creative reviews, launch checklists, test plans, and post-send retrospectives.
16- Production boundary: separate recommendation from execution.
17- Evidence boundary: say which source material supports the recommendation.
18- Review boundary: identify the human owner for risky changes.
19- Data boundary: do not assume missing fields, consent, or suppression state.
20- Platform boundary: describe provider-specific steps in operational language.
21- Measurement boundary: define what success or recovery will look like.
22- Handoff boundary: make the next step clear to another agent.
23- Rollback boundary: name the safest way to undo live-system changes.
24- Escalation boundary: stop when legal, compliance, DNS, or sending authority is unclear.
25
26## When To Use
27
28Use this skill for campaign briefs, audience logic, creative QA, launch readiness, and post-send analysis. It is designed for agent workflows where email work must be specific, reviewable, and safe across planning, drafting, implementation, QA, or operational handoff.
29
30## Operating Workflow
31
321. Start with the campaign brief: objective, audience, offer, send window, success metric, constraints, and approval owner.
332. Validate audience logic before copy, including inclusions, exclusions, consent, suppression, and expected recipient count.
343. Review creative for promise match across subject, preview, body, proof, CTA, landing page, and follow-up path.
354. Prepare launch QA: links, tracking, personalization, rendering, plain-text fallback, footer, and reply handling.
365. For analysis, compare performance against baseline, segment, source, and hypothesis rather than judging one metric alone.
376. Return a launch decision or retrospective with next actions and risks.
38
39## Review Criteria
40
41- The campaign has one primary goal and one primary CTA.
42- Audience eligibility and exclusions are written in operational terms.
43- The creative does not promise more than the landing page delivers.
44- Post-send analysis includes deliverability and list-quality context.
45- Recommendations separate immediate fixes from future tests.
46
47## Output Pattern
48
49Return campaign briefs, audience QA tables, creative reviews, launch checklists, test plans, and post-send retrospectives. 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