Hermes Email Skill
Move quickly, but make the launch state explicit. Focus on the decision a human needs now: hold, fix, approve, or monitor.
Agent Contract
The agent may inspect, reason, draft, critique, and prepare handoffs for fast delivery decisions, message QA, launch coordination, and concise status handoffs.
- Primary lens: fast delivery decisions, message QA, launch coordination, and concise status handoffs.
- Common request signals: preflight checklists, launch-room summaries, transactional copy reviews, escalation notes, and send readiness calls.
- Default posture: Move quickly, but make the launch state explicit. Focus on the decision a human needs now: hold, fix, approve, or monitor.
Use Cases
Typical requests include preflight checklists, launch-room summaries, transactional copy reviews, escalation notes, and send readiness calls.
Runbook
- State the launch context: what is sending, to whom, through which provider, and by what deadline.
- Find the blocking risk first: incorrect audience, broken personalization, deliverability issue, compliance issue, missing approval, or unclear CTA.
- Run a compressed preflight across copy, links, rendering, segment logic, exclusions, sender identity, and tracking.
- Summarize the current status in decision language: ready, ready with caveats, blocked, or needs review.
- When triaging an incident, create a timeline of observed behavior, suspected cause, blast radius, mitigation, and next owner.
- Keep all live send, resend, cancellation, suppression, and DNS actions behind explicit approval.
Quality Bar
- The status can be understood by a launch-room participant in under a minute.
- Critical defects are separated from polish issues.
- The recommended action names the owner and deadline.
- Transactional and lifecycle messages preserve the user promise exactly.
- Monitoring notes include what to watch after approval.
Output Pattern
Return launch summaries, preflight tables, incident timelines, transactional copy notes, and approve-or-hold recommendations. 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: hermesemailskill3description: Use when Codex, Hermes, OpenClaw, Claude Code, Cowork, or another AI agent needs to plan, review, implement, audit, or improve email work focused on fast delivery decisions, message QA, launch coordination, and concise status handoffs. Triggers include requests about preflight checklists, launch-room summaries, transactional copy reviews, escalation notes, and send readiness calls.4---5
6# Hermes Email Skill
7
8Move quickly, but make the launch state explicit. Focus on the decision a human needs now: hold, fix, approve, or monitor.
9
10## Agent Contract
11
12The agent may inspect, reason, draft, critique, and prepare handoffs for fast delivery decisions, message QA, launch coordination, and concise status handoffs.
13
14- Primary lens: fast delivery decisions, message QA, launch coordination, and concise status handoffs.
15- Common request signals: preflight checklists, launch-room summaries, transactional copy reviews, escalation notes, and send readiness calls.
16- Default posture: Move quickly, but make the launch state explicit. Focus on the decision a human needs now: hold, fix, approve, or monitor.
17
18## Use Cases
19
20Typical requests include preflight checklists, launch-room summaries, transactional copy reviews, escalation notes, and send readiness calls.
21
22## Runbook
23
24- State the launch context: what is sending, to whom, through which provider, and by what deadline.
25- Find the blocking risk first: incorrect audience, broken personalization, deliverability issue, compliance issue, missing approval, or unclear CTA.
26- Run a compressed preflight across copy, links, rendering, segment logic, exclusions, sender identity, and tracking.
27- Summarize the current status in decision language: ready, ready with caveats, blocked, or needs review.
28- When triaging an incident, create a timeline of observed behavior, suspected cause, blast radius, mitigation, and next owner.
29- Keep all live send, resend, cancellation, suppression, and DNS actions behind explicit approval.
30
31## Quality Bar
32
33- The status can be understood by a launch-room participant in under a minute.
34- Critical defects are separated from polish issues.
35- The recommended action names the owner and deadline.
36- Transactional and lifecycle messages preserve the user promise exactly.
37- Monitoring notes include what to watch after approval.
38
39## Output Pattern
40
41Return launch summaries, preflight tables, incident timelines, transactional copy notes, and approve-or-hold recommendations. 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