# Coordinate Email Launch Readiness

Email launches can fail when teams miss audience, copy, link, or approval risks. This skill helps Claude, Codex, and Claude Code produce fast QA checks, launch summaries, and approval-ready handoffs.

## Install

```bash
npx skillstore add sequenzy/hermesemailskill
```

## Metadata

- Status: approved
- Slug: sequenzy-hermesemailskill
- Skillstore revision: r1
- Version status: missing
- Tree hash: 1a6a7176aa5498f79e2d5c676e6c16b3c3c2ffbfd611f66eda2acc81d5930434
- Author: Sequenzy
- GitHub username: Sequenzy
- License: MIT
- Repository: https://github.com/Sequenzy/skills/tree/main/skills/hermesemailskill
- 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: 75
- Public page: https://skillstore.pages.dev/skills/sequenzy-hermesemailskill
- Manifest: https://skillstore.pages.dev/api/skills/sequenzy-hermesemailskill/manifest

## Capabilities

- Creates launch readiness summaries using ready, caveated, blocked, or needs review decisions.
- Builds compressed preflight checks for copy, links, rendering, segments, sender identity, and tracking.
- Reviews transactional and lifecycle email copy for subject, CTA, and promise consistency.
- Drafts incident timelines with observed behavior, suspected cause, blast radius, mitigation, and owner.
- Separates analysis from live email actions and requires explicit approval for high-risk changes.

## Use Cases

- Preflight a Marketing Send: Check audience, exclusions, copy, links, sender identity, tracking, and approval status before launch.
- Review Transactional Copy: Compare the message promise, subject line, CTA, merge tags, and fallback values before deployment.
- Summarize an Email Incident: Create a concise timeline, blast radius, mitigation status, next owner, and monitoring plan.

## Prompt Templates

### Basic Send Readiness Check

```
Use $hermesemailskill to review this email send brief. Tell me if it is ready, blocked, or needs review. Include copy, links, audience, exclusions, sender identity, tracking, and approval checks.
```

### Transactional Message QA

```
Use $hermesemailskill to audit this transactional email. Check whether the subject, CTA, body copy, merge tags, fallback values, footer, and user promise are consistent.
```

### Launch Room Status Handoff

```
Use $hermesemailskill to turn these notes into a launch-room handoff. Separate blockers, caveats, owner actions, approval status, deadline, and post-send monitoring.
```

### Incident Timeline and Mitigation Plan

```
Use $hermesemailskill to analyze this email incident evidence. Build a timeline, identify suspected causes, estimate blast radius, name mitigation options, and list approval gates before live changes.
```

## Limitations

- Does not send email, import contacts, edit DNS, or change production automation by itself.
- Requires accurate campaign details, test sends, segment rules, and provider status to make useful recommendations.
- Does not replace legal, compliance, deliverability, or brand approval for regulated sends.
- Cannot verify live rendering or delivery behavior without supplied evidence from tools or providers.

## Best Practices

- Provide the full send brief, audience rules, exclusions, test links, deadline, and approval chain.
- Ask for a decision summary that separates blockers from polish issues.
- Keep live sends, imports, DNS changes, and suppression edits behind explicit human approval.

## Anti Patterns

- Do not ask the skill to approve a live send without test evidence and an approval owner.
- Do not treat draft copy feedback as compliance, legal, or deliverability clearance.
- Do not combine incident diagnosis with live production changes in one unapproved step.

## Security Audit

- Audited at: 2026-07-06T19:55:27.548\+00:00
- Summary: Static analysis reported no suspicious patterns across the three prompt-only files. Manual review found no prompt injection attempts, data exfiltration intent, executable code, network behavior, or requests to bypass approval gates.

## Stats

- Views: 1
- Downloads: 7
- Favorites: 0
- Popularity score: 0