send-cold-email
Skill298 starsChanged 6 months agoMITView on GitHub
Send a cold email campaign or single message via the configured email provider (Instantly by default), optionally pre-drafting the sequence. Use when the user says 'send a cold email to this list', 'fire the email sequence', 'launch the email campaign', 'send the drip sequence', or 'email these qualified leads'. Side-effecting — calls Instantly API and writes to local SQLite + Notion.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- AddisonHoff/sendsetstheir own version, first seen Sep 26, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- AddisonHoff/sendsets★ 1same 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 repository37 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- answer-linkedin-commentsSkill
- build-routineSkill
- campaign-dashboardSkill
- campaign-strategySkill
- claap-weekly-recapSkill
- cross-platform-schedulerSkill
- debuggerSkill
- enrich-with-signalsSkill
- find-lookalikesSkill
- fullenrich-content-engagersSkill
- fullenrich-event-attendeesSkill
- fullenrich-network-activationSkill
- fullenrich-plg-reverse-lookupSkill
- icp-importSkill
- import-leadsSkill
- integrate-with-yalcSkill
- launch-linkedin-campaignSkill
- lemlist-campaign-from-icpSkill
- list-adaptersSkill
- lost-deal-revival-agentSkill
- notion-reviewSkill
- personalize-messageSkill
- predictleads-dashboardSkill
- predictleads-lookalikesSkill
- predictleads-signalsSkill
- prospect-discovery-pipelineSkill
- provider-builderSkill
- qualify-leadsSkill
- research-prospectSkill
- run-competitive-intelSkill
- run-doctorSkill
- scrape-post-engagersSkill
- setupSkill
- show-routineSkill
- track-campaignsSkill
- yalc-orientationSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Distinctive: line 58
Default cadence: day 0, day 3, day 7, day 14.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
Send Cold Email
I'll wrap two CLIs — email:create-sequence (drafts the sequence) and email:send (fires it). Both side-effecting → both shell-out.
When This Skill Applies
- "send a cold email to this list"
- "fire the email sequence"
- "launch the email campaign"
- "send the drip sequence"
- "email these qualified leads"
NOT this skill (use launch-linkedin-campaign instead):
- "launch a LinkedIn campaign" — that's the connect+DM flow on LinkedIn.
NOT this skill (use personalize-message instead):
- "personalize a single email" — single per-lead variant, not bulk send.
Workflow
Step 0 — Ask for inputs
"Which result set, what subject + intro, how many touches?"
Step 1 — Validate (result set exists, intro non-empty)
Step 2 — Shell out to email:create-sequence
npx tsx src/cli/index.ts email:create-sequence --result-set <id> --subject "<subject>" --intro "<intro>"(Verify exact flags via --help.)
Step 3 — Render the drafted sequence + ask for approval
"Drafted N messages across M touches. Send? (yes / preview only / cancel)"
Step 4 — On yes, shell out to email:send
npx tsx src/cli/index.ts email:send --sequence-id <id>Step 5 — Render send result + offer follow-ups
"Want me to (a) track replies via
track-campaigns, (b) personalize follow-ups for hot replies?"
Notes
- Requires
INSTANTLY_API_KEY(or whatever email provider is configured). - Default cadence: day 0, day 3, day 7, day 14.
- The CLI enforces sending limits per the user's email accounts (Instantly handles deliverability).
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.

