SERVICE INTEGRATION / VoltAgent
Email delivery infrastructure engineer
Organizes email authentication, provider events, suppression and monitoring around an observed sending profile.
“Use this agent when configuring email authentication, integrating transactional or marketing email providers, diagnosing deliverability problems, or building compliant sending infrastructure.”
01 / THE REASONING
Why this made the selection.
- The workflow connects SPF/DKIM/DMARC changes to provider events, global suppression and transactional-versus-bulk domain separation.
- It calls for staged policies, reputation checkpoints, provider-specific pacing and explicit rollback triggers.
- The profile aligns SPF, DKIM, and DMARC, separates sandbox credentials from production credentials, and honours suppression requests.
- It treats inbox placement as something to measure from provider signals, not as a number this file has already achieved.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- categories/07-specialized-domains/email-deliverability-engineer.md (complete definition)
- LICENSE (applicable redistribution terms)
- Host custom-agent documentation; repository installation guidance where applicable
Our findings
- The workflow connects SPF/DKIM/DMARC changes to provider events, global suppression and transactional-versus-bulk domain separation.
- It calls for staged policies, reputation checkpoints, provider-specific pacing and explicit rollback triggers.
- The checklist asks for aligned SPF, DKIM, and DMARC, suppression of hard bounces, and unsubscribe handling within 24 hours.
- Provider integration explicitly separates sandbox credentials from production credentials.
- Declared tools are Read, Write, Edit, Bash, Glob, and Grep.
- A sample progress object and a sample completion sentence state specific bounce, complaint, and placement figures. The file does not say those figures were measured, and this review did not send mail.
Not established by this review
- No agent was installed or invoked. Host/model compatibility, task accuracy and runtime behaviour were not tested.
- The resource was not executed and its tools were not called.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Use the role in your project.
- Read the pinned definition and MIT licence; review the host permissions before use.
- Place the reviewed definition in .claude/agents/, provide the required service context directly and restrict edits/network actions to the intended test environment.
- Provide sending domains/providers, authorized DNS context and real bounce/complaint/delivery evidence.
Before you start
- Claude Code and a supported model
- The relevant provider sandbox, local code and separately configured tools
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/VoltAgent/awesome-claude-code-subagents/blob/408d3c9eee2d0c75c12a3abb5de29e53c2ca6b9e/categories/07-specialized-domains/email-deliverability-engineer.md
Supports: Workflow, inputs and outputs, Declared tools and constraints, Selection and limitations
https://github.com/VoltAgent/awesome-claude-code-subagents/blob/408d3c9eee2d0c75c12a3abb5de29e53c2ca6b9e/LICENSE
Supports: Licence and attribution requirements
https://code.claude.com/docs/en/sub-agents.md
Supports: Host setup and permission defaults