This skill covers transactional and alert email for any provider with an HTTP send API, such as Resend, SES or Postmark. It commits each message durably with its event, sends under a lease, classifies every provider answer, and settles an unanswered send by idempotency key or a search before any resend.
It states what remains possible, a rare duplicate, so the product’s copy never promises exactly-once. It also covers unsubscribe headers, confirmation emails, one provider server per environment and tracking switched off.
What You Get
- Twelve binding rules from the outbox trigger and receipts to logs that hold ids and counts only
- A four-way classification of provider answers: sent, failed, retry and unanswered
- A settle procedure using idempotency keys or a metadata search after the lease
- One-click unsubscribe by POST with a deterministic HMAC token
- A test list: retries, dropped answers, crashes, racing senders and stale claims
Common Use Cases
- Adding incident or invoice emails to a SaaS
- Fixing duplicate or missing emails after a crash
- Adding an unsubscribe link that mail scanners cannot trigger
- Keeping development mail from reaching customers
What Makes It Unique
It says there is no exactly-once and names the narrow cases that remain, so copy and terms promise at least once with rare duplicates. It also makes development redirect all mail to the provider’s discard address and makes production refuse that setting, so a copied env file cannot send everything to one address.
Under The Hood
The skill is instructions and one reference file, with no scripts. Following it, the agent writes database triggers, migrations, a sender and tests in the product, and runs the tests against a real Postgres. The sender it designs calls the email provider’s HTTP API and may search its sent history. The agent runs a drill against the provider’s real API with discard addresses, using a provider token the owner supplies, and sets DNS records for the sender domain with the owner.