Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agentsCold Email Sequence Builder
A structured cold email architect that builds high-conversion, mobile-optimized 5-email sequences.
$7
Cold Email Sequence Builder
Example session with this skill installed
I'm selling a SOC2 compliance automation tool to CTOs at Series A startups who just posted jobs for Security Engineers. Our proof is helping Vanta-scale companies get audit-ready in 2 weeks.
- Read your context and instructions
- Compiled the cold email sequence
- Generated the document
I have mapped your sequence based on the hiring trigger for Security Engineers. This signals an immediate need for compliance infrastructure before the new hire starts.
Cold Outreach Sequence: SOC2 Automation for CTOs
| Day | Angle | Subject Lines | Word Count |
|---|---|---|---|
| 0 | Observation | 1. security engineer hire<br>2. audit-ready by start date<br>3. the open security role | 82 |
| 3 | Proof | 1. 2-week compliance<br>2. your soc2 timeline<br>3. series a audit data | 88 |
| 7 | Resource | 1. soc2 hiring checklist<br>2. for your new lead<br>3. compliance gap doc | 75 |
| 12 | Reframe | 1. hiring vs. automation<br>2. the security bottleneck<br>3. scale without overhead | 94 |
| 18 | Break-up | 1. moving on<br>2. soc2 timing<br>3. closing this thread | 62 |
Email 1: The Observation (Day 0)
Saw you're bringing on a new Security Engineer this month. Usually, that means the SOC2 backlog is getting heavy enough to need a dedicated head. We help Series A teams get audit-ready in two weeks so your new hire can focus on product security instead of spreadsheets. Worth a look?
Email 2: The Proof (Day 3)
A similar Series A fintech was spending 20 hours a week on evidence collection. They shifted to our automation and hit audit-readiness in 14 days flat. Should I send the case study?
Email 3: The Resource (Day 7)
I put together a short checklist of the 5 things most CTOs miss when onboarding their first security lead. No ask, just thought it might help your new hire hit the ground running. [Link: Checklist]
Email 4: The Reframe (Day 12)
Most founders assume security engineers should handle the manual compliance lift. At your stage, that's a $180k/year distraction from building your core product. Is compliance on your list this quarter?
Email 5: The Break-up (Day 18)
I haven't heard back, so I'll stop here. I thought we could save your new lead significant manual work on SOC2. If it's just bad timing, tell me when to come back.
Next steps
- Verify SPF/DKIM/DMARC on your sending domain.
- Load these into your sequencer with the suggested 3, 7, 12, 18 day spacing.
- Remove open-tracking pixels from Email 1 to maximize delivery.
cold-email-sequence-builder.pdf
PDF · document
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
The problem
Cold outreach fails when every email says the same thing or focuses on the sender instead of the recipient. Most sequences get ignored or marked as spam because they lack a clear trigger and overwhelm the reader with long blocks of text.
What it does
- Generates a five-stage sequence using distinct psychological angles: Observation, Proof, Resource, Reframe, and Break-up.
- Enforces strict brevity constraints, keeping all emails under 120 words to ensure they fit on mobile screens.
- Produces three specific subject line variations per email: lowercase fragments, problem-based, and noun-based.
- Provides a technical deliverability audit to protect your domain reputation and ensure inbox placement.
Why this beats prompting it yourself
Generic prompts often produce corporate fluff and "just checking in" bumps that trigger spam filters. This skill enforces a "them-first" architecture, preventing the AI from opening with your company history and ensuring Email 3 remains a value-only touchpoint with no ask, which earns the right to continue the sequence.
Use cases
- Building an outbound sequence for a new product launch based on specific market triggers.
- A/B testing the opening hook for a high-value prospect list.
- Refactoring existing low-performing templates into mobile-optimized, high-intent messages.
Known limitations
Does not support sequences longer than five emails. Requires a specific recipient trigger to be effective; generic "spray and pray" inputs will be rejected.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 12 days ago
- Passed all security checks, Safe to install