# Plan Safer Email Campaigns

Email campaigns can fail when briefs, audiences, creative, and launch checks are reviewed separately. This skill gives Claude, Codex, and Claude Code a structured workflow for campaign QA and analysis.

## Install

```bash
npx skillstore add sequenzy/emailcampaignskill
```

## Metadata

- Status: approved
- Slug: sequenzy-emailcampaignskill
- Skillstore revision: r1
- Version status: missing
- Tree hash: f322ca0e4f491767d9f0b7621c94b6a09b9c50c2983bb05a8069674c70c10429
- Author: Sequenzy
- GitHub username: Sequenzy
- License: MIT
- Repository: https://github.com/Sequenzy/skills/tree/main/skills/emailcampaignskill
- Ref: e397ce5a135369cd6def89cb6400d013e2f68f2f
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Quality score: 74
- Public page: https://skillstore.pages.dev/skills/sequenzy-emailcampaignskill
- Manifest: https://skillstore.pages.dev/api/skills/sequenzy-emailcampaignskill/manifest

## Capabilities

- Builds campaign briefs with objective, audience, offer, send window, success metric, constraints, and approval owner.
- Reviews audience logic for inclusions, exclusions, consent, suppression state, and expected recipient count.
- Checks creative alignment across subject, preview, body, proof, CTA, landing page, and follow-up path.
- Produces launch QA covering links, tracking, personalization, rendering, plain-text fallback, footer, and reply handling.
- Analyzes post-send performance against baselines, segments, sources, and campaign hypotheses.
- Separates recommendations from live execution and identifies approval gates for risky changes.

## Use Cases

- Prepare a Launch Brief: Turn a campaign request into a clear brief with audience rules, success metrics, constraints, and approval ownership.
- Audit Audience and Creative: Review segment logic, suppressions, consent, copy, links, tracking, and landing page alignment before launch.
- Run a Post-Send Retrospective: Compare campaign results against baseline performance, segment behavior, deliverability context, and the original hypothesis.

## Prompt Templates

### Create a Campaign Brief

```
Create an email campaign brief from this request. Include objective, audience, offer, send window, success metric, constraints, and approval owner.
```

### Review Audience Logic

```
Review this audience plan for inclusions, exclusions, consent, suppressions, expected count, and risky assumptions. Return issues and approval questions.
```

### Audit Creative and Launch Readiness

```
Audit this email campaign for promise match, CTA clarity, links, tracking, personalization, rendering, footer, reply handling, and launch blockers.
```

### Analyze Results and Recommend Next Tests

```
Analyze these campaign results against the baseline, segments, source, and hypothesis. Separate immediate fixes, future tests, and unresolved risks.
```

## Limitations

- Does not send emails or change production systems on its own.
- Does not replace legal, compliance, DNS, or sending authority review.
- Requires accurate source material about audiences, consent, suppressions, and benchmarks.
- Provider-specific guidance stays operational and may need current vendor documentation.

## Best Practices

- Provide the brief, audience rules, creative, links, tracking plan, and approval requirements together.
- Validate consent, suppression logic, and expected recipient count before reviewing copy quality.
- Separate recommendations from live-system actions and require approval for high-risk changes.

## Anti Patterns

- Asking the skill to send email, import contacts, or edit suppressions without explicit approval.
- Judging performance from one metric without baselines, segment context, or deliverability data.
- Assuming missing consent, audience fields, legal approvals, or sending authority are acceptable.

## Security Audit

- Audited at: 2026-07-06T19:45:36.234\+00:00
- Summary: Static analysis reported no suspicious patterns in the three prompt-only files. Manual review found operational safety boundaries and no prompt injection, exfiltration intent, executable code, or requests to bypass review.

## Stats

- Views: 0
- Downloads: 4
- Favorites: 0
- Popularity score: 0