Automatic Cold Email Mailbox Provisioning

What it does

This skill replaces the manual chain of buying a domain → configuring DNS → creating SMTP → uploading to a sending platform, by integrating a mailbox provisioning provider's instant order API. It includes idempotency keys to avoid duplicate orders and exports generated credentials securely.

When to use it

• When you need to scale cold email infrastructure fast (many new domains and mailboxes)
• When manual DNS and SMTP setup has become a bottleneck
• When you want to avoid duplicate charges from retrying an order that failed halfway

Steps

1. Define how many domains and mailboxes are needed and under what brand/theme
2. Generate a unique idempotency key for the order
3. Present the estimated cost and wait for explicit approval before any charge
4. Submit the async order via the provisioning provider's API
5. Monitor order status until domains, DNS, and SMTP are ready
6. Export generated credentials securely (never as plain text in chat)

The skill

---
name: cold-email-mailbox-provisioning
description: Orders domains, DNS, SMTP, and upload to the sending platform in a single async order via API, with an approval gate before any charge.
---

# Automatic Cold Email Mailbox Provisioning

## 1. Purpose
Replace the manual chain of buy domain → DNS → SMTP → upload to sending platform with a single async API order, turning hours of work into minutes.

## 2. Order definition
Specify how many domains and mailboxes are needed, the domain theme/brand, and the destination sending platform.

## 3. Charge approval gate
Since this process involves a real charge, the estimated cost is always presented and explicit approval is required before confirming the order.

## 4. Idempotency
Every order carries a unique idempotency key, so a retry from a network error doesn't cause a duplicate charge.

## 5. Order monitoring
The order is async: status is polled periodically until domains, DNS, and SMTP are provisioned and verified.

## 6. Credential export
Generated credentials (SMTP, domain access) are exported to a secure store or environment file, never written as plain text in the conversation.

## 7. Safety rules
- No charge is confirmed without explicit user approval.
- Domain counts or costs are never invented; real provider data is used.
- No SMTP credential or API key is ever exposed in chat.

For Claude Code, save it as ~/.claude/skills/cold-email-mailbox-provisioning/SKILL.md. In Cursor, ChatGPT or another assistant, paste it as project instructions.