Index of every page on this site: llms.txt
All skills
n8n-io avatar

/cold-email

@273d130 official
by n8n - Workflow Automationn8n-io/n8n211k stars
61,599
Run it yourself

Write B2B cold emails, subject lines, and follow-up sequences that read like a person wrote them. Use when the user wants a cold outreach email or a follow-up, or asks why an opener, a reason to reach out, or an email gets no replies.

  • 6 files
  • 25.5 KB
  • Updated 4 days ago
  • GitHub
Use this Skill: https://skilld.dev/gh/n8n-io/n8n/cold-email

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencessubject-lines.md

≈754 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Subject Line Optimization

The subject line determines whether the email gets read. The data is counterintuitive: short, boring, internal-looking subject lines win decisively.

Length: 2–4 words

  • 2-word subject lines get 60% more opens than 5-word (Lavender).
  • Going from 2 to 4 words reduces replies by 17.5%.
  • 2–4 words yield 46% open rates vs 34% for 10 words (Belkins, 5.5M emails).
  • Mobile truncates at 30–35 characters — brevity is practical necessity.

Internal Camouflage Principle

Subject lines that look like they came from a colleague, not a vendor, double open rates (Gong). Buyers mentally categorize before opening — if it looks like sales, it's filtered.

High-performing examples: "reply rates" · "trial delays" · "hiring ops" · "employee turnover" · "Q2 forecast" · "new patients" · "personalization issue" · "second page"

Capitalization: lowercase wins

All-lowercase has highest open rates (Gong, 85M+ emails). Lowercase looks more personal/internal. For cold outreach specifically, lowercase beats title case.

Personalization: context over name

Personalized subject lines boost opens 26–50%, but type matters:

  • First name in subject line → 12% fewer replies. Signals automation.
  • Contextual personalization works: pain points, competitors, trigger events, industry challenges.
  • Use {{painPoint}}, {{competitor}}, {{commonGround}} — not {{firstName}}.

Questions: only when highly specific

Data conflicts: Belkins says questions perform well (46% open rate). Lavender says questions lower opens by 56%. Resolution: specific pain questions work ("Need help with {{challenge}}?"), generic questions fail ("Quick question?" / "Have 15 minutes?"). Default to statements.

What to Avoid

Anti-pattern Impact
Salesy language ("increase," "boost," "ROI") -17.9% opens
Urgency words ("ASAP," "urgent") Below 36% opens
Excessive punctuation ("!!!" or "??") -36% opens
Numbers and percentages -46% opens
Emojis Hurt B2B professionalism
Pitching product in subject -57% replies
Empty/no subject line +30% opens but -12% replies
Spam triggers ("free," "guarantee," "act now") Deliverability risk

C-Suite Subject Lines

Executives receive 300–400 emails daily, decide in seconds. They respond 23% more often than non-C-suite when emails pass their filter (6.4% reply rate).

What works: ultra-concise, human, understated. "{{companyInitiative}}" · "thank you" · "an update" · "a question" · reference to a specific project or trigger event.

Anything "salesy" is immediately rejected.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 273d130. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 4 days ago
metadata
{
  "version": "2.2.4"
}

README badge

README badge for n8n-io/n8n/cold-email