Individual skill

inbox-lifecycle-manager

The weekly keep/cancel/promote/buy loop for a cold email sending fleet. Decides which domains are burned and should be cancelled, which warmed reserves to promote into campaigns, which capacity to demote, and how many new domains to buy — using measured reply, bounce, age and send-volume floors instead of gut feel. Use when asked "which inboxes should I cancel", "what should I replace this week", "my fleet costs too much", "I'm under my send goal", or as the Friday hygiene routine.

skills/inbox-lifecycle-manager/SKILL.md

Read pinned source

Source commit 25c5d85fbb5dd3efec97b0ca457cbbc286547476

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
814
Repository last updated
Oct 5, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Inbox Lifecycle Manager

**Diagnosis tells you a domain is sick. This skill decides whether it dies.**

Every cold email fleet leaks money in two directions at once: you keep paying for burned domains
that will never reply again, and you run under your send goal because nobody promoted the warmed
reserves sitting idle. This is the weekly loop that fixes both, with an approval gate in the
middle so nothing gets cancelled on a hunch.

**Read-only by default.** The plan step writes nothing, anywhere. Only the apply step, run after
an explicit human "yes", changes a tag, a campaign, or a provider subscription.

## When to use
Back to top