launch-campaign
Skill8 starsChanged 6 months agoMITView on GitHub
Pre-flight audit of a Smartlead campaign before going live, then start it. Verifies sequences, mailboxes, leads, schedule, warmup health, and tracking-domain CNAME. Refuses to launch with broken state. Use when the user says they want to launch, start, go live with, or kick off a campaign that's already configured.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- EricStrohmaier/adchat-mcptheir own version, first seen Nov 16, 2026
- nickmerich/artist-led-events-skillstheir own version, first seen Nov 8, 2026
- fliqrlabs/instagram-creator-skillstheir own version, first seen Nov 1, 2026
- vindreshsingh/engineering-skillstheir own version, first seen Oct 20, 2026
- teachskillofskills-ai/DigitalMarketingPro-techshutheir own version, first seen Oct 11, 2026
- link7373/agentic-sales-marketingtheir own version, first seen Aug 8, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- indranilbanerjee/digital-marketing-pro★ 934same name
- fliqrlabs/instagram-creator-skills★ 5same name
- EricStrohmaier/adchat-mcp★ 1same name
- link7373/agentic-sales-marketing★ 1same name
- nickmerich/artist-led-events-skills★ 0same name
- teachskillofskills-ai/DigitalMarketingPro-techshu★ 0same name
- vindreshsingh/engineering-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- audit-mailbox-configSkill
- check-deliverabilitySkill
- clone-campaignSkill
- compare-campaignsSkill
- create-campaignSkill
- smartlead-onboardingSkill
- spam-testSkill
- upload-leadsSkill
- warmup-mailboxesSkill
- weekly-reportSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 7 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Run these in order. If any check fails, surface it and ASK before proceeding.
- Very specific: line 27
If status is ACTIVE already, tell the user and stop.
- Distinctive: line 35
Should return ≥1. Zero = won't send anything.
- Distinctive: line 43
Should return ≥1. Zero = nothing to send from.
- Distinctive: line 51
Should return ≥1. Zero = ask user if empty start is intentional.
- Very specific: line 73
Should resolve to open.sleadtrack.com..
- Very specific: line 88
If campaign timezone is America/New_York but lead list is heavy on EU domains, surface it.
- Distinctive: line 107
After launch, tell the user to check back in 1-2 hours:
- Distinctive: line 114
Bounce rate: if it crosses 5% in the first hour, PAUSE immediately and triage
- Distinctive: line 115
Sends per hour: should match expected throughput from schedule + mailbox count
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “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.
/launch-campaign
You're doing pre-flight checks on a campaign that's been built, then starting it.
What you need from the user
- Campaign ID to launch
- (Optional) Permission to auto-fix obvious issues vs. just report them
Pre-flight checklist
Run these in order. If any check fails, surface it and ASK before proceeding.
Check 1 — Campaign exists and is in DRAFTING / PAUSED status
smartlead campaigns get <id> --output json | jq '{id, name, status}'If status is ACTIVE already, tell the user and stop.
Check 2 — At least 1 sequence step
smartlead campaigns sequences <id> --output json | jq 'length'Should return ≥1. Zero = won't send anything.
Check 3 — At least 1 mailbox assigned
smartlead campaigns email-accounts <id> --output json | jq 'length'Should return ≥1. Zero = nothing to send from.
Check 4 — Leads uploaded
smartlead leads list <id> --output json | jq 'length'Should return ≥1. Zero = ask user if empty start is intentional.
Check 5 — All assigned mailboxes are warmed up
smartlead campaigns email-accounts <id> --output json | \
jq -r '.[].email_account_id' | \
while read mb_id; do
smartlead accounts get $mb_id --output json | \
jq -r --arg id "$mb_id" '{id: $id, warmup: .warmup_details.status, reputation: .warmup_details.warmup_reputation}'
doneFlag any mailbox with warmup.status != ENABLED or reputation < 80%.
Check 6 — Custom tracking domain CNAME resolves (if tracking is enabled)
For each mailbox with custom_tracking_domain set:
dig +short CNAME <tracking_domain>Should resolve to open.sleadtrack.com.. If empty, link wrapping and open pixels will fail.
Check 7 — Settings sanity
smartlead campaigns get <id> --output json | jq '.settings'Flag if:
enable_ai_esp_matching: trueAND campaign has both Gmail+Outlook senders (seedocs/learnings/esp-matching-analysis.md)track_settingsincludesDONT_TRACK_*but recipient list looks audit-aware (Big Tech etc.)- Schedule looks wrong (sending on weekends, 24/7 window, etc.)
Check 8 — Schedule timezone matches recipient audience
If campaign timezone is America/New_York but lead list is heavy on EU domains, surface it. Sending at 9 AM ET = 3 PM CEST = late afternoon for EU recipients.
Launch decision
Once all checks pass (or user explicitly waves off warnings):
smartlead campaigns start <id>Confirm activation:
smartlead campaigns get <id> --output json | jq '.status'
# Should now show "ACTIVE"First-hour monitoring
After launch, tell the user to check back in 1-2 hours:
smartlead campaigns analytics <id>What to watch:
- Bounce rate: if it crosses 5% in the first hour, PAUSE immediately and triage
- Sends per hour: should match expected throughput from schedule + mailbox count
- Auto-replies / out-of-office: Smartlead handles these (stop-on-auto-reply default)
If something goes wrong post-launch
To stop sending (drains queued sends — this is what you usually want):
smartlead campaigns stop <id>NOT pause — pause doesn't drain queued sends and the analytics endpoint lies about it (see docs/learnings/settings-api-quirks.md quirk 6).
Reference
docs/learnings/settings-api-quirks.md— campaign status verbs, pause-drain behaviordocs/learnings/esp-matching-analysis.md— why to disable AI ESP matchingdocs/learnings/mailbox-warmup-best-practices.md— what "warmed up" actually means
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.

