agentleFS
Sign inStart free
prosyo-aiprosyo-ai/gtm-skill/skills/domain-warmup-plan/SKILL.md

domain-warmup-plan

Skill13 starsChanged 23 days agoMITView on GitHub

Use this skill when you set up new domains or mailboxes for cold email and need a warm-up plan: \"how do I warm up a new domain\", \"warm-up schedule for new inboxes\", \"how fast can I ramp sending\". Plans domain purchase and setup, a week-by-week warm-up and ramp schedule per mailbox, the health checks that gate each step up, and what to do when a mailbox shows trouble. Produces a ramp calendar and capacity forecast for the whole sending infrastructure.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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
  1. Distinctive:

    Use this before sending any cold email from new domains or mailboxes.

    line 16
  2. Distinctive:

    Start date and when the first campaign needs to go out.

    line 22
  3. Distinctive:

    Never move up a week if bounces exceed 2%, any spam complaint arrives, or placement tests show spam.

    line 49
  4. Distinctive:

    MUST wait at least two weeks of warm-up before any cold sends.

    line 62
  5. Distinctive:

    MUST gate each ramp step on bounce, complaint and placement checks.

    line 63
  6. Distinctive:

    NEVER use domains that imitate another company's brand.

    line 64
  7. Distinctive:

    NEVER exceed 50 cold emails per mailbox per day.

    line 65

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Use this before sending any cold email from new domains or mailboxes. New senders have no reputation; ramping too fast is the most common way to burn a domain in its first month.

Inputs

  • Target cold volume per day across the team.
  • Domains and mailboxes planned (or let the plan size them).
  • Start date and when the first campaign needs to go out.

The play

1. Size the infrastructure

Mailboxes needed = target daily cold volume ÷ 30-40 per mailbox. Domains needed = mailboxes ÷ 3. Add 20% spare capacity so a mailbox can rest without missing targets.

Example: 600 cold emails a day ÷ 30 = 20 mailboxes; ÷ 3 = 7 domains; plus spare = 24 mailboxes across 8 domains.

2. Set up correctly on day 0

  • Domains close to the brand (variations of the company name), never misleading look-alikes of other brands.
  • SPF, DKIM, DMARC published and passing; MX records set; domain redirects to the main site.
  • Real sender names, photos, signatures.

3. Warm, then ramp

WeekWarm-up emails per dayCold emails per dayGate to move on
15-10, rising0Authentication passing
215-200No spam placement in tests
320-305-10 to best-fit verified contactsBounces < 2%, replies arriving
420-3015-20Bounces < 2%, complaints ~0
520-3025-30Placement in inbox
6+Keep 10-20 running30-40Weekly checks stay green

Warm-up means real, two-way conversations with engaged inboxes. Keep a low level running while cold sending continues.

4. Gate every step

Never move up a week if bounces exceed 2%, any spam complaint arrives, or placement tests show spam. Hold the current level for another week instead.

5. Plan the capacity curve

Show when the team reaches full volume. Usually week 6. If the campaign must start sooner, start with fewer, better contacts rather than more volume.

What good looks like

  • First cold sends go to the cleanest, best-fit contacts, which builds reputation from real replies.
  • The plan includes spare mailboxes and a resting rotation.
  • The common mistake is buying ten domains on Monday and sending 50 a day from each by Friday.

Rules

  • MUST wait at least two weeks of warm-up before any cold sends.
  • MUST gate each ramp step on bounce, complaint and placement checks.
  • NEVER use domains that imitate another company's brand.
  • NEVER exceed 50 cold emails per mailbox per day.

Example prompts

  • "We want to send 500 cold emails a day starting next month. Plan the domains, mailboxes and warm-up."
  • "I just set up 3 new mailboxes. Give me a week-by-week ramp."
  • "Our new domain got 4% bounces in week 3. What now?"

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free