warmup-mailboxes
Skill8 starsChanged 6 months agoMITView on GitHub
Apply a verified production-grade warmup configuration to one or many Smartlead mailboxes. Sets the golden config (1 → 20 ramp, 60% reply rate, 15 send/day, weekday warmups). Use when the user has new mailboxes that need to be warmed up, when they're seeing poor inbox placement on a mature mailbox, or when they ask about "warmup settings" / "golden config" / "best practices for warmup".
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- audit-mailbox-configSkill
- check-deliverabilitySkill
- clone-campaignSkill
- compare-campaignsSkill
- create-campaignSkill
- launch-campaignSkill
- smartlead-onboardingSkill
- spam-testSkill
- upload-leadsSkill
- weekly-reportSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Ask for these if not provided.
- Distinctive: line 76
After ~3 weeks of clean warmup, the mailbox is ready for production.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Before running: verify exact flag names with
smartlead <command> --help. Flag shapes shown below are illustrative — confirm against the actual CLI.
/warmup-mailboxes
You're configuring warmup on one or more Smartlead mailboxes using a verified production-grade config.
What you need from the user
- Mailbox IDs — comma-separated, or a tag/client filter
- Warmup pool key — a 5-letter-prefix-5-letter-suffix tag like
acme1-pool1(groups mailboxes that warm up together) - Optionally: client_id if the mailboxes need to be assigned to a Smartlead client record
Ask for these if not provided.
The golden config we'll apply
Verified for Gmail mailboxes. Before applying, check the mailbox type — if it's not GMAIL, pause and ask the user how they want to proceed.
message_per_day: 15 # not 20 — leave buffer for warmup
warmup_enabled: true
warmup_min_count: 1
warmup_max_count: 20
daily_rampup: 5 # 1 → 6 → 11 → 16 → 20 over 5 days
reply_rate: 60 # 60% reply rate from warmup network
auto_adjust_warmup: false # manual control beats automatic
send_warmups_only_on_weekdays: true
use_custom_domain: false # OFF during warmup, turn on week 4+
daily_reply_limit: 5Why these values: see docs/learnings/mailbox-warmup-best-practices.md.
How to run it
For a single mailbox
smartlead accounts warmup <mailbox_id> --enable \
--daily 20 --rampup 5 --reply-rate 60 \
--warmup-key <pool-key>For many mailboxes (uses the internal bulk endpoint)
smartlead accounts bulk-update \
--ids <id1>,<id2>,<id3> \
--message-per-day 15 \
--warmup-status ENABLED \
--warmup-min 1 \
--warmup-max 20 \
--rampup-value 5 \
--reply-rate 60 \
--warmup-key <pool-key> \
--send-warmups-only-on-weekdaysFilter by tag (if mailboxes are pre-tagged)
# Find IDs by tag
smartlead accounts tags get --tag <tag-id> --output json | jq -r '.[].id' > ids.txt
# Then bulk-update
smartlead accounts bulk-update --ids-file ids.txt ...After warming up
After ~3 weeks of clean warmup, the mailbox is ready for production. At that point:
# Turn on custom-domain tracking (was off during ramp)
smartlead accounts bulk-update --ids <ids> --use-custom-domainVerification
smartlead accounts get <mailbox_id> --output json | jq '.warmup_details'Should show:
warmup_enabled: truetotal_warmup_per_day: 20warmup_min_count: 1warmup_max_count: 20daily_rampup: 5warmup_key_id: "<pool-key>"
Notes
- The public warmup API enforces
daily_rampup >= 5. To use lower rampup values you must use the internal bulk endpoint (which thebulk-updatecommand uses by default). warmup_key_idcontrols which mailboxes pool together for warmup. Pick keys deliberately — seedocs/learnings/warmup-key-id-format.md.- For a deep dive on why send 15 (not 20) and why weekday-only, see
docs/learnings/mailbox-warmup-best-practices.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

