email-warmup

Create gradual email volume ramp schedules for new sending domains and IPs.

2|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/chunkydotdev/email-skills --skill email-warmup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: email-warmup
Source: https://github.com/chunkydotdev/email-skills/tree/main/skills/deliverability/email-warmup
Command: npx skills add https://github.com/chunkydotdev/email-skills --skill email-warmup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

New sending domains and IPs have no established reputation with mailbox providers, so sudden high-volume sends are indistinguishable from spammer activity, triggering deferrals, spam folder placement, or outright blocks that can take weeks to recover from.

Core Features & Use Cases

  • Tailored warmup schedules: Custom volume ramps for high-volume marketing, per-mailbox cold outreach, and transactional email, with strict 2x daily volume increase rules to avoid triggering spam filters.
  • Provider-specific guidance: Built-in instructions for Amazon SES, SendGrid, Postmark, and Resend, including how to leverage each platform's native warmup automation features.
  • AI agent safeguards: Specialized guardrails for AI-driven sending, including infrastructure-level rate limits, per-recipient cooldowns, and negative signal monitoring to prevent accidental reputation damage from agent bugs or loops.
  • Use case example: A team launching a new marketing domain can use this skill to follow a 28-day gradual volume ramp, send first to their most engaged contacts, and monitor bounce/complaint rates to avoid spam folder placement.

Quick Start

Use the email-warmup skill to create a 28-day gradual sending volume schedule for your new marketing domain, starting with 50 emails on day 1 and ramping up to full volume by day 29, while prioritizing sends to your most recently engaged contacts.

Frequently Asked Questions about email-warmup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my new sending domain go to the spam folder when I start sending high volumes?

New sending domains and IPs lack established reputation, causing mailbox providers to treat sudden high-volume sends as spam. Gradual volume ramping builds sender trust by slowly increasing daily email throughput to avoid triggering spam filters and reputation damage.

How do I warm up a dedicated IP for email sending?

Warm up a dedicated IP by implementing a gradual volume ramp schedule, starting with a low daily volume like 50 emails and increasing throughput over a 28-day period. Enforcing a 2x daily volume increase cap prevents deferrals, blocks, and spam folder placement during IP warmup.

Do I need to warm up my email domain after switching email providers?

Yes, warming up email domains is required after switching providers, migrating to dedicated IPs, or resuming sends after 30+ days of inactivity. Gradual volume ramps rebuild sender reputation with mailbox providers to prevent spam filter triggers and deliverability damage.

Does this email warmup approach work with Amazon SES and SendGrid?

Yes, the email warmup process includes provider-specific guidance for Amazon SES, SendGrid, Postmark, and Resend, providing tailored instructions to leverage each platform's native warmup automation features for marketing bulk, cold outreach, and transactional email streams.

How do I prevent reputation damage when scaling AI agent email sending?

Prevent AI agent email reputation damage by applying specialized guardrails including infrastructure-level rate limits, per-recipient cooldowns, and negative signal monitoring. These safeguards stop accidental volume spikes from agent bugs or loops from triggering spam filters.

What is the best way to prioritize recipients during an email warmup schedule?

The best way to prioritize recipients during email warmup is engagement-based targeting. Send first to your most recently engaged contacts and monitor bounce and complaint rates closely to maintain deliverability and avoid spam folder placement.