create-campaign
Skill8 starsChanged 6 months agoMITView on GitHub
Create a new Smartlead campaign from scratch — name, schedule, settings, sequences, sender mailboxes, and leads. Walks the user through the 6 setup steps interactively, with sane defaults for cold email. Use when the user says they want to create / launch / start a new campaign, set up an outbound campaign, or build something from scratch in Smartlead.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- Ken-Technology/cold-email-skillstheir own version, first seen Nov 1, 2026
- PitterLopes/google-ads-claude-plugintheir own version, first seen Nov 1, 2026
- Talkif-ai/skillstheir own version, first seen Sep 13, 2026
- VapiAI/skillstheir own version, first seen Sep 3, 2026
- getnao/sylphtheir own version, first seen May 19, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- getnao/sylph★ 195same name
- VapiAI/skills★ 69same name
- Ken-Technology/cold-email-skills★ 5same name
- PitterLopes/google-ads-claude-plugin★ 0same name
- Talkif-ai/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
- launch-campaignSkill
- smartlead-onboardingSkill
- spam-testSkill
- upload-leadsSkill
- warmup-mailboxesSkill
- weekly-reportSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Ask these one at a time (don't overwhelm with a 10-question form):
- Distinctive: line 62
Stop on reply → don't keep emailing people who already replied
- Distinctive: line 64
Ask the user if they want to override any of these.
- Distinctive: line 68
Ask the user for their sequence — usually 2-4 emails.
- Very specific: line 101
If the user has a CSV ready, invoke /upload-leads to handle this step.
- Very specific: line 105
Before invoking smartlead campaigns start <id>, verify:
- Distinctive: line 112
If any check fails, surface it.
- Distinctive: line 134
If bounce rate >5% in the first day, pause and triage.
“Common” is measured: kept by at least 6 in 10 of the 4 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.
/create-campaign
You're walking the user through creating a brand-new Smartlead campaign end-to-end.
What you need from the user
Ask these one at a time (don't overwhelm with a 10-question form):
- Campaign name — e.g., "Q1 Founders Outbound"
- Client (optional) — if they run a multi-tenant Smartlead account, which client this campaign belongs to. Skip if not applicable.
- Target audience size — rough lead count. Drives mailbox sizing.
- Lead source — do they have a CSV ready, or should we set up the campaign empty?
- Sender mailboxes — by tag, by ID, or "use all my warmed-up mailboxes"
- Schedule — timezone, sending window (default: 9-5 weekdays in the user's TZ)
The 6 setup steps
Step 1 — Create the campaign shell
smartlead campaigns create --name "<name>" \
${CLIENT_ID:+--client-id $CLIENT_ID}Save the returned campaign_id.
Step 2 — Set the schedule
smartlead campaigns schedule <campaign_id> \
--timezone "America/New_York" \
--days 1,2,3,4,5 \
--start-hour 09:00 \
--end-hour 17:00 \
--min-time-between-emails 10 \
--max-new-leads-per-day 50Defaults to weekday business hours unless the user specifies otherwise. days: 0=Sunday through 6=Saturday.
Step 3 — Settings (deliverability-safe defaults)
smartlead campaigns settings <campaign_id> \
--no-track-email-open \
--no-track-link-click \
--no-ai-esp-matching \
--stop-on-reply \
--stop-on-auto-replyWhy these defaults:
- Open/click tracking OFF → plain-text feel, fewer spam signals (see
docs/learnings/mailbox-warmup-best-practices.md) - AI ESP matching OFF → it routes Google recipients wrong (see
docs/learnings/esp-matching-analysis.md) - Stop on reply → don't keep emailing people who already replied
Ask the user if they want to override any of these.
Step 4 — Add the email sequence
Ask the user for their sequence — usually 2-4 emails. If they have a draft, paste it. Otherwise offer a starter template.
smartlead campaigns sequences <campaign_id> --add-step \
--seq-number 1 \
--subject "{{personalization_hook}}" \
--body @email1.html \
--delay-days 0
smartlead campaigns sequences <campaign_id> --add-step \
--seq-number 2 \
--subject "Re: {{previous_subject}}" \
--body @email2.html \
--delay-days 4(Same for each follow-up step.)
Step 5 — Assign sender mailboxes
# By IDs
smartlead campaigns email-accounts <campaign_id> --add --ids <id1>,<id2>,<id3>
# Or by tag
smartlead accounts tags get --tag-id <tag_id> --output json | jq -r '.[].id' > mailboxes.txt
smartlead campaigns email-accounts <campaign_id> --add --ids-file mailboxes.txtSizing rule of thumb: at golden config (15 sends/mailbox/day), 1 mailbox can handle ~75 leads/week. For 1,000 leads, plan ~15 mailboxes.
Step 6 — Upload leads
If the user has a CSV ready, invoke /upload-leads to handle this step. Otherwise leave the campaign without leads — they can add them later.
Pre-launch checklist (before starting)
Before invoking smartlead campaigns start <id>, verify:
- ✅ At least 1 sequence step exists
- ✅ At least 1 mailbox assigned
- ✅ Leads uploaded (or user confirms empty start is OK)
- ✅ Schedule + settings are sane
- ✅ All assigned mailboxes have completed warmup (
/audit-mailbox-config)
If any check fails, surface it. Don't auto-fix without asking.
Start the campaign
smartlead campaigns start <campaign_id>Or if they want to schedule a future start:
smartlead campaigns schedule <campaign_id> --schedule-start-time "2026-06-01T13:00:00Z"
smartlead campaigns start <campaign_id>After launch — what to monitor
Tell the user to check back in 24-48 hours with:
smartlead campaigns analytics <campaign_id>— sends + bounce rate/check-deliverability <campaign_id>— full audit
If bounce rate >5% in the first day, pause and triage.
Reference
docs/learnings/campaign-cloning-runbook.md— full 6-step API detailsdocs/learnings/settings-api-quirks.md— field translation gotchasdocs/learnings/mailbox-warmup-best-practices.md— sender pool health
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.

