Deployment

Transactional Email Deliverability

Designs secure, reliable transactional email: sender setup, idempotent triggers, bounce and suppression handling.

What it does

Designs secure, reliable transactional email: sender setup, idempotent triggers, bounce and suppression handling.

When to use it

Use for receipts, verification, password and status emails, and end-to-end delivery evidence.

Problems it prevents

Stops a password-reset or receipt email that silently never arrives, with nobody able to prove why.

Typical workflow

  1. Define message contracts and triggers
  2. Configure sending and authentication responsibly
  3. Build resilient retry and suppression handling
  4. Verify end-to-end delivery evidence

Example output

A transactional email with an idempotent trigger and documented proof it was actually sent and received.

What's included

  1. 01
    The complete prompt

    The full manual as a ready-to-save SKILL.md file, matched exactly to what ships in the T7 library.

  2. 02
    Install walkthrough

    Personal (~/.claude/skills/) and project (.claude/skills/) folder instructions, whichever fits how you work.

  3. 03
    Use notes

    How Claude invokes it, what a good result looks like, and what to check before you trust the output.

Installation

Save the manual as SKILL.md in ~/.claude/skills/transactional-email-deliverability/ to use it on every project, or in .claude/skills/transactional-email-deliverability/ to scope it to one repository. Then invoke it directly:

/transactional-email-deliverability

Read the official Claude Code skills guide

Works well with