# Plan Safe Agent Email Workflows

Email work often spans agents, tools, approvals, and live systems, which raises execution risk. This skill structures handoffs, QA checks, and approval gates before action.

## Install

```bash
npx skillstore add sequenzy/emailagentskill
```

## Metadata

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

## Capabilities

- Classifies agent roles for research, strategy, copy, implementation, QA, analysis, and operations.
- Defines what agents may read, draft, change, or execute in email workflows.
- Creates tool handoff plans with inputs, outputs, acceptance criteria, and risk levels.
- Adds checkpoints for segmentation, legal claims, production edits, and performance interpretation.
- Produces audit-friendly status reports and next actions for another agent.

## Use Cases

- Coordinate a Campaign Handoff: Map roles, inputs, outputs, QA checks, and approvals before agents draft or prepare campaign assets.
- Review an Email Automation Change: Separate recommendation, implementation, QA, and approval steps for a risky automation update.
- Audit Multi-Agent Email Work: Create an audit trail of assumptions, evidence, decisions, unresolved risks, and human owners.

## Prompt Templates

### Plan a Basic Email Task

```
Use this skill to plan my email task. Define the agent role, source materials, allowed actions, approval needs, QA checks, and next step.
```

### Create a Tool Handoff

```
Create a tool handoff spec for this email workflow. Include inputs, expected outputs, acceptance criteria, risk level, owner, and approval gate.
```

### Review a Production Change

```
Review this proposed email production change. Separate recommendation from execution, list evidence, identify risks, require approvals, and define rollback steps.
```

### Design a Multi-Agent Operating Model

```
Design a multi-agent operating model for this email program. Assign roles, handoffs, checkpoints, evidence requirements, approval gates, status reporting, and recovery paths.
```

## Limitations

- Does not send email, import contacts, or change live production systems.
- Does not replace legal, privacy, deliverability, or brand review.
- Requires source materials and system context for precise recommendations.
- Provider-specific steps remain operational guidance, not direct platform automation.

## Best Practices

- Name the human owner before any high-risk email action.
- Record assumptions, source materials, decisions, and rejected options.
- Define rollback steps before production edits or live sends.

## Anti Patterns

- Asking an agent to send, import, or change production settings without explicit approval.
- Passing vague email tasks between agents without inputs, outputs, or acceptance criteria.
- Treating performance analysis or legal claims as final without review.

## Security Audit

- Audited at: 2026-07-06T21:12:42.984\+00:00
- Summary: Static analysis found no suspicious patterns in this prompt-only skill. Manual review found safety-oriented instructions for agent handoffs, approval gates, audit trails, and live email system boundaries. No semantic security findings were identified.

## Stats

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