cold-email
Write and optimize B2B cold email outreach sequences that get replies, covering personalization, follow-up cadence, deliverability, and…
You say
- Context cost
- 15.3k tokensestimated from the bundle, loaded when it triggers
- Bundle
- 4 files · 61.3 kB3 scripts among them — read before you run
- Licence
- MITpaid listing
- Last change
- —v1.0.0
- Servers it uses
- Noneruns standalone
What it does
Write and optimize B2B cold email outreach sequences that get replies, covering personalization, follow-up cadence, deliverability, and compliance. Use when writing cold outreach, prospecting/SDR emails, or building outbound sequences.
Installed, it changes the agent in these ways.
What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.
And these are the jobs people reach for it for.
Expertise
Domain judgement the base model does not have.
Filed under
The skill itself
This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.
SKILL.md22.9 kB · 555 lines
---
name: cold-email
description: >
Write and optimize B2B cold email outreach sequences that get replies, covering
personalization, follow-up cadence, deliverability, and compliance. Use when
writing cold outreach, prospecting/SDR emails, or building outbound sequences.
license: MIT
metadata:
version: 1.0.0
author: borghei
category: marketing
domain: outbound
updated: 2026-03-09
---
15# Cold Email Outreach
16
17Production-grade B2B cold email that sounds like it came from a person, not a sequence tool.
18
19---
20
21## Table of Contents
22
23- [Keywords](#keywords)
24- [Quick Start](#quick-start)
25- [Core Workflows](#core-workflows)
26- [Writing Principles](#writing-principles)
27- [Voice Calibration by Audience](#voice-calibration-by-audience)
28- [Subject Line Framework](#subject-line-framework)
29- [Follow-Up Strategy](#follow-up-strategy)
30- [Personalization Framework](#personalization-framework)
31- [Deliverability Setup](#deliverability-setup)
32- [Compliance Requirements](#compliance-requirements)
33- [Anti-Patterns](#anti-patterns)
34- [Best Practices](#best-practices)
35- [Integration Points](#integration-points)
36
37---
38
39## Keywords
40
41cold email, cold outreach, prospecting email, SDR email, sales email, first-touch email, follow-up sequence, email prospecting, outbound email, sales development, sequence building, email personalization, email deliverability, CAN-SPAM, GDPR, B2B outreach, email compliance, subject lines, reply rates, breakup email
42
43---
44
45## Clarify First
46
47Before generating the email, confirm these inputs. If any is unknown or vague, ASK — do not assume:
48
49- [ ] **ICP / prospect context** — job title, company type/size, seniority (drives the opener, relevance, and voice calibration)
50- [ ] **Specific problem + outreach trigger** — the pain and why now (selects the framework and shapes the opener)
51- [ ] **The one proof point** — a specific number, named customer, or result (drives the credibility line)
52- [ ] **The single CTA / goal** — book a call, get a reply, or get a referral (drives the one ask)
53
54Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
55
56## Quick Start
57
58### Write a First-Touch Email
59
601. Define the ICP, specific problem, and outreach trigger
612. Select voice calibration based on recipient seniority
623. Write opener about their world (not yours)
634. State relevance in 1-2 sentences with specific proof
645. Close with a single, low-friction ask
656. Generate 3 subject line variants
667. Validate: under 150 words, no corporate speak, one CTA
67
68### Build a Full Sequence
69
701. Write the first email (above)
712. Plan 4-5 follow-ups, each with a different angle
723. Set escalating gap cadence (Day 1, 4, 9, 16, 25, 35)
734. Write each follow-up as a standalone (recipient does not remember earlier emails)
745. End with a breakup email that closes the loop professionally
756. Validate deliverability setup before sending
76
77---
78
79## Core Workflows
80
81### Workflow 1: Single First-Touch Email
82
83**Step 1: Gather Context**
84
85Required information:
86- **Sender context**: Role, company, what they sell, key proof points
87- **Prospect context**: Job title, company type/size, likely problem, trigger for outreach
88- **Goal**: Book a call? Get a reply? Get a referral?
89
90**Step 2: Choose Framework**
91
92| Framework | Best When | Structure |
93|-----------|-----------|-----------|
94| Problem-First | Prospect has a visible pain point | Problem observation > Relevance > Ask |
95| Trigger-Based | There is a specific event (funding, hiring, news) | Trigger reference > Connection to problem > Ask |
96| Mutual Connection | Referral or shared network | Name drop > Context > Ask |
97| Value-First | You have something genuinely useful to share | Insight/resource > Brief context > Ask |
98| Direct Ask | Prospect is high-intent or very senior | Brief context > Direct question |
99
100**Step 3: Draft the Email**
101
102Structure:
103```
104Subject: [2-4 words, looks like an internal email]
105
106[Opener: 1 sentence about their world — trigger, observation, or question]
107
108[Relevance: 1-2 sentences connecting their situation to what you do]
109
110[Proof: 1 sentence of credible evidence — specific number, named customer, result]
111
112[Ask: 1 sentence with a single, specific, low-friction CTA]
113
114[Sign-off]
115```
116
117**Step 4: Validate**
118
119- [ ] Under 150 words total
120- [ ] Opener is about them, not you
121- [ ] No sentence starts with "I" or "We"
122- [ ] One CTA, not multiple
123- [ ] CTA is a question, not a statement
124- [ ] No jargon or corporate speak
125- [ ] Would a friend send this to another friend in business?
126
127### Workflow 2: Full Sequence Build
128
129**Step 1: Write Email 1 (Using Workflow 1)**
130
131**Step 2: Plan Follow-Up Angles**
132
133Each follow-up needs a distinct angle. Plan before writing:
134
135| Email | Day | Angle | What is New |
136|-------|-----|-------|-------------|
137| 1 | Day 1 | Problem-first | Initial outreach |
138| 2 | Day 4 | New evidence | Case study, data point, or recent result |
139| 3 | Day 9 | Different pain point | Alternative angle on their world |
140| 4 | Day 16 | Industry insight | Something notable about their space |
141| 5 | Day 25 | Direct question | Simple, clear ask without context |
142| 6 | Day 35 | Breakup | Professional close, referral ask |
143
144**Step 3: Write Each Follow-Up**
145
146Rules for every follow-up:
147- Standalone: does not require reading previous emails
148- New angle: brings something the previous email did not
149- Shorter than Email 1 (each subsequent email gets shorter)
150- Never says "just checking in" or "circling back"
151- Never references all previous emails ("As I mentioned in my last three emails...")
152
153**Step 4: Write the Breakup Email**
154
155The breakup email closes the loop. It signals this is the last one, which paradoxically increases reply rate.
156
157Template:
158```
159Subject: closing the loop
160
161[Name],
162
163Last note from me. If [specific problem] becomes a priority,
164reply here and I'll pick it up.
165
166If there's someone else at [Company] better suited for this
167conversation, a name would help.
168
169Either way — [genuine well-wish related to something specific].
170
171[Sign-off]
172```
173
174### Workflow 3: Performance Iteration
175
176**Step 1: Diagnose the Problem**
177
178| Symptom | Likely Cause | Fix |
179|---------|-------------|-----|
180| Low open rate (< 25%) | Subject lines | Test new subject line patterns |
181| Opens but no replies (< 2% reply rate) | Email body | Rewrite with stronger relevance and lower-friction CTA |
182| Replies but wrong outcome | CTA mismatch | Adjust the ask |
183| High bounce rate (> 5%) | List quality | Verify email addresses before sending |
184| Landing in spam | Deliverability | Check SPF/DKIM/DMARC, reduce send volume, warm domain |
185
186**Step 2: Rewrite the Underperforming Element**
187
188Focus on one element at a time. Do not rewrite the entire email when only the subject line is the problem.
189
190**Step 3: Test and Measure**
191
192- A/B test subject lines with minimum 100 sends per variant
193- Test one variable at a time
194- Wait for 3-5 days of data before drawing conclusions
195- Document every test and result for future reference
196
197---
198
199## Writing Principles
200
201### 1. Write Like a Peer, Not a Vendor
202
203The moment your email sounds like marketing copy, it is deleted.
204
205**Test:** Would you send this to a smart colleague at another company? If not, rewrite.
206
207### 2. Every Sentence Earns Its Place
208
209Each sentence must do one of these jobs:
210- Create curiosity
211- Establish relevance
212- Build credibility
213- Drive to the ask
214
215If a sentence does none of these, cut it.
216
217### 3. Personalization Must Connect to the Problem
218
219Generic personalization is worse than none.
220
221- Bad: "I saw you went to Stanford" followed by a pitch unrelated to Stanford
222- Good: "I saw you're hiring three SDRs — usually a signal that you're scaling cold outreach. That's exactly the challenge we help with."
223
224The personalization must bridge to the reason for reaching out.
225
226### 4. Lead with Their World, Not Yours
227
228The opener should be about their situation, problem, or context. Not about you or your product.
229
230### 5. One Ask Per Email
231
232Do not ask them to book a call, watch a demo, read a case study, AND reply with their timeline. Pick one.
233
234---
235
236## Voice Calibration by Audience
237
238| Audience | Length | Tone | Subject Style | What Works |
239|----------|--------|------|---------------|------------|
240| C-suite (CEO, CRO, CMO) | 3-4 sentences | Ultra-brief, peer-level, strategic | Short, vague, internal-looking | Big problem > relevant proof > one question |
241| VP / Director | 5-7 sentences | Direct, metrics-conscious | Slightly more specific | Specific observation + clear business angle |
242| Manager | 7-10 sentences | Practical, shows homework | Can be descriptive | Specific problem + practical value + easy CTA |
243| Technical (Engineer, Architect) | 7-10 sentences | Precise, no fluff | Technical specificity | Exact problem > precise solution > low-friction ask |
244| Founder / Solo | 5-7 sentences | Empathetic, peer-to-peer | Casual, human | Shared experience + relevant proof + conversational ask |
245
246Rule: The higher up the org chart, the shorter your email needs to be.
247
248---
249
250## Subject Line Framework
251
252### Principles
253
254The goal of a subject line is to get the email opened. Not to convey value, not to be clever. Just opened.
255
256The best cold email subject lines look like internal emails: short, slightly vague, enough curiosity to click.
257
258### Patterns That Work
259
260| Pattern | Example | Why It Works |
261|---------|---------|-------------|
262| Two or three words | "quick question" | Looks like a real email from a colleague |
263| Specific trigger + question | "your TechCrunch piece" | Specific enough to not look like spam |
264| Shared context | "re: Series B" | Feels like a follow-up, not cold |
265| Observation | "your ATS setup" | Relevant, not salesy |
266| Referral hook | "[mutual name] suggested I reach out" | Social proof front-loaded |
267| Role-specific | "SDR team scaling" | Shows you know who they are |
268
269### Patterns That Kill Opens
270
271- ALL CAPS anything
272- Emojis in subject lines
273- Fake Re: or Fwd: (damages trust before the first word)
274- Question format ("Are you struggling with X?") — sounds like an ad
275- Company name mention ("Acme Corp: helping you achieve...")
276- Blog headline format ("5 ways to improve your...")
277- Exclamation marks
278
279---
280
281## Follow-Up Strategy
282
283### Cadence
284
285| Email | Send Day | Gap | Notes |
286|-------|----------|-----|-------|
287| Email 1 | Day 1 | — | First touch |
288| Email 2 | Day 4 | +3 days | New evidence angle |
289| Email 3 | Day 9 | +5 days | Different pain point |
290| Email 4 | Day 16 | +7 days | Industry insight |
291| Email 5 | Day 25 | +9 days | Direct question |
292| Breakup | Day 35 | +10 days | Close the loop |
293
294Gaps increase over time. Persistent but not annoying.
295
296### Follow-Up Angle Rotation
297
298| Angle Type | Description | Example |
299|-----------|-------------|---------|
300| New evidence | Case study, data point, recent result | "Since my last note, we helped [Company] reduce [metric] by [%]" |
301| Different pain | Alternative problem in their world | "Setting aside [topic A] — are you dealing with [topic B]?" |
302| Industry insight | Something notable about their space | "Saw [industry trend]. Most teams are responding by [approach]" |
303| Direct question | Simple ask without buildup | "[Name], quick one: who handles [function] at [Company]?" |
304| Reverse ask | Request for referral | "If this isn't your area, who would you point me to?" |
305| Social proof | Relevant peer doing it | "[Similar company] just went through this — here's what worked" |
306
307---
308
309## Personalization Framework
310
311### Three Tiers of Personalization
312
313**Tier 1: Segment-Level (Minimum)**
314- Industry-specific pain points
315- Company size-specific challenges
316- Role-specific language and priorities
317
318**Tier 2: Company-Level (Standard)**
319- Recent company news (funding, hiring, product launch)
320- Tech stack signals (what tools they use)
321- Growth signals (job postings, office expansion)
322
323**Tier 3: Individual-Level (Premium)**
324- Content they have published (posts, articles, talks)
325- Career moves (new role, promotion)
326- Shared connections or experiences
327- Specific project or initiative they are leading
328
329### Personalization Sources
330
331| Source | What You Find | How to Use |
332|--------|--------------|-----------|
333| LinkedIn profile | Role, tenure, content they share | Role-specific opener, reference their posts |
334| Company blog | Priorities, culture, technology choices | Connect your solution to their stated priorities |
335| Job postings | Growth areas, pain points, tech stack | "You're hiring for X, which usually means..." |
336| Press/news | Funding, partnerships, launches | Trigger-based openers |
337| GitHub/tech blogs | Technical decisions, stack choices | Technical relevance and credibility |
338| Podcast/talks | Opinions, expertise areas | "Your point about X in [talk] resonated..." |
339
340---
341
342## Deliverability Setup
343
344### Infrastructure Requirements
345
346| Component | What | Why |
347|-----------|------|-----|
348| Dedicated sending domain | mail.yourdomain.com or outreach.yourdomain.com | Protects primary domain reputation |
349| SPF record | DNS TXT record authorizing sending servers | Proves you are authorized to send |
350| DKIM signing | Cryptographic signature on emails | Proves emails were not modified in transit |
351| DMARC policy | DNS record specifying SPF/DKIM enforcement | Tells receiving servers how to handle failures |
352| Domain warmup | 4-6 weeks of gradually increasing volume | Builds sender reputation with ISPs |
353
354### Warmup Schedule
355
356| Week | Daily Volume | Notes |
357|------|-------------|-------|
358| 1 | 10-20 | Send to engaged contacts only |
359| 2 | 20-40 | Mix of warm and cold contacts |
360| 3 | 40-70 | Begin cold outreach at low volume |
361| 4 | 70-100 | Monitor bounce rates closely |
362| 5-6 | 100-150 | Increase if bounce rate < 3% |
363| 7+ | 150-200 max | Steady state for cold outreach |
364
365### Deliverability Monitoring
366
367- Bounce rate: Keep under 3% (above 5% damages reputation)
368- Spam complaint rate: Keep under 0.1%
369- Verify email addresses before sending (use verification services)
370- Monitor blacklists monthly (MXToolbox, Google Postmaster)
371- Use mail-tester.com to check deliverability score before campaigns
372
373### Email Format Rules
374
375- Plain text or minimal HTML (no logos, images, or heavy formatting)
376- No tracking pixels if possible (they trigger spam filters)
377- Limit links to 1-2 maximum
378- Avoid spam trigger words: "free," "guarantee," "act now," "limited time"
379- Keep emails under 200 words
380- Include a physical address (CAN-SPAM requirement)
381- Include an unsubscribe mechanism
382
383---
384
385## Compliance Requirements
386
387### CAN-SPAM (United States)
388
389Required for all commercial email to US recipients:
390- [ ] Sender identity is clear and not misleading
391- [ ] Subject line is not deceptive
392- [ ] Physical postal address included
393- [ ] Opt-out mechanism present and functional
394- [ ] Opt-out requests honored within 10 business days
395- [ ] Message identified as an advertisement (if applicable)
396
397### GDPR (European Union)
398
399Required for email to EU/EEA residents:
400- [ ] Legitimate interest basis documented for B2B outreach
401- [ ] Prospect data collected from lawful sources
402- [ ] Privacy notice accessible
403- [ ] Data processing records maintained
404- [ ] Right to erasure honored promptly
405- [ ] Data minimization: only collect what you need
406- [ ] No consent required for B2B if legitimate interest applies, but this must be documented and defensible
407
408### CASL (Canada)
409
410Required for commercial electronic messages to Canadian recipients:
411- [ ] Express or implied consent documented
412- [ ] Sender identification clear
413- [ ] Unsubscribe mechanism functional
414- [ ] Implied consent valid for 2 years from last transaction or 6 months from inquiry
415
416### Best Practice Regardless of Jurisdiction
417
418- Always include an easy unsubscribe option
419- Honor opt-outs immediately (do not wait the legal maximum)
420- Do not buy email lists (poor quality, compliance risk)
421- Document your legal basis for outreach
422- Keep records of consent and opt-out requests
423
424---
425
426## Anti-Patterns
427
428| Pattern | Why It Fails |
429|---------|-------------|
430| "I hope this email finds you well" | Instant signal that this is templated mass outreach |
431| "I wanted to reach out because..." | Three words of nothing before saying anything |
432| Opening with "My name is X and I work at Y" | They can see your name. Start with something useful. |
433| Feature dump in email 1 | Nobody cares about features when they do not trust you yet |
434| HTML templates with logos and colors | Looks like marketing, gets spam-filtered |
435| Fake Re:/Fwd: subject lines | Deceptive, destroys trust |
436| "Just checking in" follow-ups | Adds no value, removes credibility |
437| Social proof without context | "We work with 500 companies" means nothing without relevance |
438| Long-form case study in email 1 | Save it for follow-up |
439| Passive CTAs ("Let me know if you're interested") | Weak. Ask a direct question or propose a specific step. |
440| Multiple CTAs in one email | Creates decision paralysis. One ask per email. |
441| Sending from your primary domain | Risks your entire domain reputation |
442
443---
444
445## Best Practices
446
4471. **Send from a real person, not a company alias** — "sarah@mail.acme.com" outperforms "sales@acme.com" every time.
448
4492. **Read the email aloud before sending** — If you hear yourself droning, cut. If it sounds like a brochure, rewrite.
450
4513. **Time your sends** — Tuesday through Thursday, 8-10 AM in the prospect's timezone, produces the highest open rates for B2B.
452
4534. **Verify emails before campaigns** — A 5% bounce rate damages your domain reputation. Verify every address.
454
4555. **Track reply rate, not open rate** — Open tracking is unreliable (privacy features block tracking pixels). Reply rate is the metric that matters.
456
4576. **Build sequences, not individual emails** — Most replies come from follow-ups, not the first email. Plan the full sequence before writing.
458
4597. **Document your playbook** — Every winning email, subject line, and angle should be documented for the team. Build institutional knowledge.
460
4618. **Respect opt-outs immediately** — Not just legally required, but professionally essential. Process within 24 hours.
462
4639. **Rotate sending domains** — Use 2-3 sending domains to distribute volume and protect reputation.
464
46510. **Segment relentlessly** — A generic template sent to 1,000 people will underperform a personalized email sent to 50 who match your ideal profile.
466
467---
468
469## Integration Points
470
471- **Copywriting** — Use for landing page copy and marketing page copy. Cold email follows different constraints (shorter, personal tone, no visual design).
472- **Content Strategy** — Use to create content assets (case studies, guides) referenced in follow-up emails.
473- **Marketing Context** — Use for ICP definition and positioning. If you do not know who you are targeting and why, cold email is the wrong tool.
474- **Marketing Psychology** — Apply psychological principles (reciprocity, social proof, scarcity) to strengthen email messaging.
475- **Campaign Analytics** — Use to track sequence performance and optimize based on data.
476
477---
478
479## Troubleshooting
480
481| Symptom | Likely Cause | Fix |
482|---------|-------------|-----|
483| Open rate below 15% | Subject lines too long, spammy, or generic | Test 2-4 word internal-email-style subjects. Run subject_line_scorer.py. |
484| Opens but reply rate below 1% | Email body lacks relevance or CTA is too high-friction | Rewrite opener about their world. Use a question CTA, not a statement. |
485| Emails landing in spam (2026) | Missing SPF/DKIM/DMARC or RFC 8058 one-click unsubscribe | Gmail/Yahoo/Microsoft now reject non-compliant bulk mail. Run deliverability_checker.py. |
486| Bounce rate above 3% | Unverified email list or role-based addresses | Verify every address before sending. Remove catch-alls and role accounts. |
487| Spam complaint rate above 0.10% | Irrelevant targeting or too-frequent sends | Gmail enforces 0.10% threshold as of 2026. Improve targeting and reduce volume per domain. |
488| Replies but wrong outcome | CTA mismatch with funnel stage | Align CTA friction to prospect readiness. C-suite wants a question; managers accept a demo link. |
489| Domain blacklisted | Sending from primary domain or too-high volume | Use dedicated sending subdomains. Warm new domains 4-6 weeks. Max 100 emails/day/address. |
490
491---
492
493## Success Criteria
494
495- Open rate consistently above 35% across sequence (benchmark: 25-40% for cold B2B)
496- Reply rate above 3% (benchmark: 2-5% for well-targeted cold outreach)
497- Bounce rate below 2% on every campaign (Gmail/Microsoft 2026 threshold)
498- Spam complaint rate below 0.10% (2026 Gmail/Yahoo hard enforcement line)
499- Deliverability rate above 95% with SPF/DKIM/DMARC/RFC 8058 fully configured
500- Sequence produces replies from emails 2-5, not just email 1 (follow-ups carry 60%+ of replies)
501- Every email under 150 words with one CTA and zero corporate speak
502
503---
504
505## Scope & Limitations
506
507**In Scope:**
508- B2B cold email outreach strategy and copy
509- Multi-email sequence design and optimization
510- Subject line and body copy frameworks
511- Deliverability infrastructure setup (SPF, DKIM, DMARC, domain warming)
512- CAN-SPAM, GDPR, CASL compliance guidance
513- Performance diagnosis and iteration methodology
514
515**Out of Scope:**
516- Email HTML template design (use email-template-builder)
517- Marketing automation platform configuration (Outreach, Salesloft, Apollo)
518- Email list building or scraping (compliance risk)
519- Warm/inbound email sequences (use email-sequence)
520- Phone call scripts or LinkedIn outreach sequences
521- Legal advice on compliance (consult legal counsel for jurisdiction-specific requirements)
522
523**Limitations:**
524- Scripts use heuristic analysis, not live inbox testing (use mail-tester.com for production validation)
525- Deliverability checker cannot perform live DNS lookups (verify SPF/DKIM/DMARC records separately)
526- Benchmarks are B2B SaaS-focused; adjust thresholds for other industries
527
528---
529
530## Python Automation Tools
531
532### 1. Subject Line Scorer (scripts/subject_line_scorer.py)
533Scores cold email subject lines on deliverability, spam risk, and open-rate potential using deterministic heuristics.
534
535```bash
536python scripts/subject_line_scorer.py "quick question"
537python scripts/subject_line_scorer.py --file subjects.txt --json
538```
539
540### 2. Deliverability Checker (scripts/deliverability_checker.py)
541Audits email content for spam triggers, HTML complexity, link density, and compliance against 2025-2026 Gmail/Yahoo/Microsoft requirements.
542
543```bash
544python scripts/deliverability_checker.py email.txt
545python scripts/deliverability_checker.py email.txt --domain yourdomain.com --json
546```
547
548### 3. Sequence Optimizer (scripts/sequence_optimizer.py)
549Analyzes cold email sequence performance data against industry benchmarks. Diagnoses open rate, reply rate, bounce rate, and cadence issues.
550
551```bash
552python scripts/sequence_optimizer.py sequence_data.json
553python scripts/sequence_optimizer.py --sample --json
554```
555
In the file
SKILL.md3,660 words
Files4
LicenceMIT
Why you can read it
Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.
What it costs in context
Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.
≈100
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
15,225
on trigger
The instruction body and 3 supporting files, read only when the skill fires.
7.7%
of a 200k window
Ten skills this size would take about 77% of the window before you open a file.
050k100k150k200k context window
15.3k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.
Servers bill, skills cost
A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.
Before and after
The same question, put to the same model twice: once as it comes, and once with these instructions loaded.
No worked example has been published for this skill yet.
Adoption
Installsnone yet
Ratingno reviews yet
The procedure it runs
The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.
Prose, not code
These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.
Servers it uses
None. This skill calls no MCP servers at all.
Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.
It writes no files and reaches no network. All it changes is how the model reasons and writes.
What it asks for
Writes filesno
Network accessno
Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.
What it will not do
Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.
What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.
If this is not it
What is in the bundle
4 files, 61.3 kB on disk. Mostly text — the instructions the model reads — with 3 scripts in it that your client would run only if the instructions tell it to.
- SKILL.md22.9 kB
- scripts/deliverability_checker.py14.5 kB
- scripts/sequence_optimizer.py14.5 kB
- scripts/subject_line_scorer.py9.4 kB
What is not in it
A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 3 scripts beside the text, so the bundle is 4 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.
Install
Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.
$35 once
cold-email · MIT · borghei
Price$35 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery release of 1.x through this account
You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.
Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.
# cold-email · 15.3k tokens when loaded
npx mcprush@latest skill add borghei/cold-emailWrites to .claude/skills/cold-email/ in the current project. Add --global to put it in your home directory instead, for every project.
Which clients pick it up on their own
A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.
Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Version1.0.0
Publishedno release date on file
Price$35
Referenceborghei/cold-email
Versions
v1.0.0 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.
v1.0.0
- No earlier releases have been published to the marketplace.
Pinning
Put borghei/cold-email@1.0.0 in the install command to hold this exact version. Without the suffix you get whatever is current the day you install, and nothing moves under you afterwards.
Reviews
—no reviews yet · no installs yet
Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.
Who can post
Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.
Who wrote it
Publisher
Servers0