agentleFS
poorvith-mppoorvith-mp/skills-sales-support/skills/cold-outreach/SKILL.md

cold-outreach

Skill0 starsChanged 2 months agoMITView on GitHub

Write cold email and DM sequences that get replies, including domain warmup and deliverability. Use when drafting personalized cold emails, LinkedIn DMs, or follow-up cadences.

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use lead-qualify, yt-search and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • kronus-techSkill

    lead-qualify

    Score and qualify an inbound lead based on budget, timeline, technical fit, and engagement signals. Auto-invoked when user says "qualify this lead", "score this lead", "is this worth pursuing".

    Also in 3 projects that use this

  • azuma520Skill

    yt-search

    Search YouTube videos, get video metadata, and download subtitles/transcripts using yt-dlp. Use when the user wants to find videos, search YouTube, look up a YouTube channel, get video info, download captions, grab subtitles, or extract a transcript. Triggers include "找影片", "搜影片", "YouTube 搜尋", "抓字幕", "逐字稿", "search videos", "find videos on YouTube", "get subtitles", "video transcript", "youtube tutorial", "watch video about", "影片推薦", "有沒有影片", "教學影片". Make sure to use this skill whenever the user mentions YouTube, video search, subtitles, or transcripts — even if they don't explicitly say "yt-search".

    Also in 3 projects that use this

  • aiskilloftheweekSkill

    proposal-generator

    Turns raw notes from a client conversation (call notes, transcript, email thread, brief, voice memo) into a ready-to-send proposal, quote or offer, with the problem in the client's own words, clear scope and exclusions, a specific price, a risk reducer, an expiry date and one dated next step. Use whenever the user needs to write, draft, finish or review a proposal, quote, estimate, offer, bid, statement of work or "preventivo", or says things like "the client asked for a quote", "turn these notes into a proposal", "I need to send them an offer". Works for any industry, offer type and client type.

    Also in 3 projects that use this

  • claude-office-skillsSkill

    email-marketing

    Email marketing automation - campaign creation, sequence building, A/B testing, deliverability optimization, and analytics

    Also in 3 projects that use this

  • indranilbanerjeeSkill

    content-repurpose

    Repurpose one content piece into 10+ channel formats with drafts and a calendar. \"repurpose this blog post\"

    Also in 3 projects that use this

  • AnthropicSkill

    pitch-deck

    Populates investment banking pitch deck templates with data from source files. Use when: user provides a PowerPoint template to fill in, user has source data (Excel/CSV) to populate into slides, user mentions populating or filling a pitch deck template, or user needs to transfer data into existing slide layouts. Not for creating presentations from scratch.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 10 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before sending a single email, configure four DNS records on every sending domain:

    line 24
  2. Very specific:

    Custom Tracking Domain (CNAME): When using tracking pixels or click tracking, use a dedicated subdomain (track.trycompany.com) with an SSL …

    line 34
  3. Distinctive:

    Keep messages under 250 characters.

    line 64
  4. Distinctive:

    Never pitch or drop a scheduling link in the connection request note.

    line 66
  5. Distinctive:

    Run every prospect email through real-time verification tools (NeverBounce, ZeroBounce) before loading into cadences.

    line 69
  6. Distinctive:

    Never send cold outreach from the primary domain used for corporate operations.

    line 73
  7. Distinctive:

    Every prospect email list must be validated immediately prior to sending.

    line 74
  8. Distinctive:

    Keep cold emails under 90 words with a single, clear question rather than multiple demands.

    line 75
  9. Distinctive:

    NEVER exceed 40 cold emails per mailbox per day.

    line 85
  10. Distinctive:

    NEVER include calendar links (Calendly/HubSpot) in initial outreach emails.

    line 86
  11. Distinctive:

    NEVER send generic template blasts that lack custom, role-specific personalization triggers.

    line 87

“Common” is measured: kept by at least 6 in 10 of the 27 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cold Outreach

Cold outreach succeeds on technical deliverability and acute relevance, not brute volume. Spray-and-pray sequences destroy domain reputation and land in spam folders. Modern outbound requires isolated secondary domain infrastructure, strict SPF/DKIM/DMARC authentication, automated warmup ramps, and tight multi-channel cadences across Email and LinkedIn.

1. Domain Infrastructure & Deliverability Protocol

Protect your primary company domain by building dedicated outbound infrastructure:

A. Secondary Domain Architecture

  • Never send cold outreach from your primary apex domain (e.g. company.com). If an outreach campaign gets flagged, primary corporate email deliverability is compromised.
  • Purchase 2–3 lookalike secondary domains (e.g. trycompany.com, usecompany.com, companyhq.com) configured with Google Workspace or Microsoft 365 mailboxes.
  • Set up 301 redirects from secondary domain roots to your primary website homepage.

B. DNS Authentication Records (Mandatory)

Before sending a single email, configure four DNS records on every sending domain:

  1. SPF (Sender Policy Framework):
    v=spf1 include:_spf.google.com ~all
  2. DKIM (DomainKeys Identified Mail): Generate a 2048-bit cryptographic key in Google Workspace / M365 admin and publish the TXT record at google._domainkey.domain.com.
  3. DMARC (Domain-based Message Authentication):
    v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@trycompany.com; pct=100; sp=quarantine
  4. Custom Tracking Domain (CNAME): When using tracking pixels or click tracking, use a dedicated subdomain (track.trycompany.com) with an SSL cert. Best practice: Disable open/click tracking entirely for cold emails to improve inbox placement.

C. Automated Domain Warmup Schedule

Warm up mailboxes for 14–21 days using automated peer networks (Smartlead, Instantly) before sending cold campaigns:

  • Week 1 (Days 1–7): 5–10 automated warmup emails/day. Zero cold prospect emails.
  • Week 2 (Days 8–14): 15–20 warmup emails/day. Start cold outbound at 5 emails/day/mailbox.
  • Week 3+ (Production): 25–35 cold emails/day + 15 warmup emails/day per mailbox.
  • Hard Ceiling: Maximum 40 cold emails per mailbox per day. To send 200 emails/day, use 5 mailboxes distributed across 2 domains.

2. Multi-Channel Cadence Architecture (Email + LinkedIn)

Structure outreach across 4–5 touches over a 16-day window:

Day 1:  [Email 1] Personal observation + problem statement + low-friction ask
Day 2:  [LinkedIn] Profile view + connection request (blank note or 1-line observation)
Day 5:  [Email 2] Quick bump with 1-sentence customer proof or metric
Day 8:  [LinkedIn DM] Short value drop if connection accepted (no calendar link)
Day 12: [Email 3] Frictionless resource or perspective shift
Day 16: [Email 4] Polite breakup closing the loop

High-Converting Email Frameworks

  • Subject Lines: 2–4 words, lowercase, non-promotional: quick question, [Company] <> [Prospect Company], re: [Specific Trigger].
  • Word Count: Strictly between 50 and 90 words. Long emails trigger cognitive fatigue on mobile screens.
  • The Low-Friction Call to Action (CTA):
    • Weak: "Can we schedule a 30-minute demo on Tuesday at 2pm? Here's my Calendly link."
    • Strong: "Open to checking out the 2-minute breakdown?" or "Worth exploring, or is this not on your radar for Q3?"

LinkedIn DM Rules

  • Keep messages under 250 characters.
  • Anchor to a public signal: comment on their recent post, hiring announcement, or podcast appearance.
  • Never pitch or drop a scheduling link in the connection request note.

3. List Hygiene & Bounce Prevention

  • Run every prospect email through real-time verification tools (NeverBounce, ZeroBounce) before loading into cadences.
  • Maintain a bounce rate strictly < 2.0%. Bounces above 3% trigger spam filtering across Google and Microsoft networks.

Critical Rules

  1. Never send cold outreach from the primary domain used for corporate operations.
  2. Every prospect email list must be validated immediately prior to sending; never send to stale or unverified lists.
  3. Keep cold emails under 90 words with a single, clear question rather than multiple demands.

Verification Checklist

  • Secondary domains configured with valid SPF, DKIM, and DMARC records.
  • Mailboxes warmed up for a minimum of 14 days with >50% warmup engagement.
  • Prospect list verified with <2% predicted bounce rate.
  • Email copy contains zero spam trigger phrases ("free", "guarantee", "act now", "urgent").
  • CTA is conversational and asks for interest rather than booking calendar time directly.

Anti-Patterns

  • NEVER exceed 40 cold emails per mailbox per day; distribute volume across multiple inboxes.
  • NEVER include calendar links (Calendly/HubSpot) in initial outreach emails; links degrade deliverability.
  • NEVER send generic template blasts that lack custom, role-specific personalization triggers.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.