agentleFS
bcharlesonbcharleson/cursor-for-gtm-demo/.cursor/skills/cold-email-deliverability/SKILL.md

cold-email-deliverability

Skill2 starsChanged 4 months agoMITView on GitHub

Audits and guides cold email deliverability — plain text sending, SPF/DKIM/DMARC, ESP setup, recipient filters, and SEG awareness. Use when reviewing sending infrastructure, inbox placement, DNS records, email authentication, spam filters, Proofpoint, Mimecast, Barracuda, or deliverability before a campaign.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. mbfinotti/sales-skills★ 3same name
    2. SkillMedev/b2b-prospecting-engine★ 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 repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    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
  1. Distinctive:

    When deliverability is in scope:

    line 16
  2. Distinctive:

    If the user explicitly wants links (calendar, deck, video):

    line 33
  3. Distinctive:

    Prefer sending the asset after a positive reply.

    line 36
  4. Distinctive:

    Ensure domain reputation, DNS auth, and landing pages are solid (see SEG section).

    line 37
  5. Distinctive:

    Every sending domain or inbox — Google Workspace, Microsoft 365, or custom SMTP — must have proper DNS authentication.

    line 41
  6. Distinctive:

    Use a dedicated outreach domain or subdomain when possible — protects primary brand domain.

    line 55
  7. Distinctive:

    Keep bounce and complaint rates low.

    line 58
  8. Distinctive:

    When ICP is enterprise or regulated (healthcare, finance, government), assume SEG presence and apply stricter infrastructure standards.

    line 90
  9. Distinctive:

    When reviewing a user's setup or draft campaign, respond with:

    line 111

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

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

Cold Email Deliverability

Deliverability is always top of mind. Legitimate cold outreach shares the same filtering environment as spam. Infrastructure and message format must earn inbox placement before copy or offers matter.

Agent Responsibilities

When deliverability is in scope:

  1. Audit before send — Check DNS auth, message format, and recipient-environment risks.
  2. Flag blockers immediately — Missing SPF, DKIM, or DMARC is a hard stop. Do not recommend sending until resolved.
  3. Default to safest format — Plain text, no links, no images, unless the user explicitly chooses otherwise.

Message Format Rules

Default (best practice)

  • Plain text only — No HTML templates, no rich formatting.
  • No links — URLs trigger marketing/spam heuristics. Omit unless intentionally doing so with eyes open on risk.
  • No images — Same rationale as links.
  • No attachments in initial cold touches — increases filter scrutiny.

When links or assets are intentional

If the user explicitly wants links (calendar, deck, video):

  • Acknowledge deliverability tradeoff.
  • Prefer sending the asset after a positive reply.
  • Ensure domain reputation, DNS auth, and landing pages are solid (see SEG section).

Sending-Side Infrastructure

Every sending domain or inbox — Google Workspace, Microsoft 365, or custom SMTP — must have proper DNS authentication.

Required DNS records

RecordPurposeAgent action
SPFAuthorizes which servers may send for the domainVerify present and includes only legitimate send sources
DKIMCryptographic signature proving message integrityVerify signing is enabled and DNS publishes the public key
DMARCPolicy for failed SPF/DKIM; reportingVerify policy exists (start with p=none for monitoring if needed, tighten over time)

If any of SPF, DKIM, or DMARC is missing or misconfigured → flag immediately. Deliverability will suffer; do not proceed as if send-ready.

Additional sending hygiene

  • Use a dedicated outreach domain or subdomain when possible — protects primary brand domain.
  • Warm new domains/inboxes gradually — volume spikes hurt reputation.
  • Align From domain with DKIM signing domain.
  • Keep bounce and complaint rates low; remove invalid addresses promptly.
  • Match reverse DNS (PTR) where applicable on custom SMTP.

Recipient-Side Environment

Prospects receive mail through varied stacks. ICP often determines the mix.

Common recipient ESPs

  • Google (Gmail / Workspace) — Strong filtering, engagement signals matter.
  • Microsoft (Outlook / M365) — Similar; sensitive to authentication failures and bulk patterns.
  • Third-party / custom SMTP — Variable rules; authentication failures are penalized heavily.

The "handshake" between sender and receiver depends on authentication, reputation, content signals, and engagement history.

SEGs (Secure Email Gateways)

Corporate inboxes often sit behind SEGs that add layers beyond native ESP filtering:

  • Proofpoint
  • Barracuda
  • Mimecast
  • Cisco IronPort / others

Implications for outreach:

  • Authentication must be flawless — SEGs are stricter than consumer Gmail.
  • Domain reputation and domain age matter more.
  • Domain masking — Sending domain should look legitimate and aligned with the business (not deceptive; professional and consistent).
  • Landing pages — If links are used later, pages must be trustworthy: valid SSL, clear business identity, no redirect chains, no mismatch between email domain and link domain.
  • Plain-text-first cold touches reduce SEG triage into "marketing" buckets.

When ICP is enterprise or regulated (healthcare, finance, government), assume SEG presence and apply stricter infrastructure standards.

Pre-Send Checklist

Copy this checklist and work through it:

Deliverability audit:
- [ ] SPF record present and correct for sending source
- [ ] DKIM enabled and DNS key published
- [ ] DMARC record present with sensible policy
- [ ] Sending domain aligned with From address
- [ ] Message is plain text (unless user opted into HTML/links)
- [ ] No links or images in initial touch (unless intentional)
- [ ] Volume appropriate for domain/inbox age
- [ ] Recipient environment considered (consumer vs corporate/SEG)
- [ ] Landing pages valid if links will be used in follow-ups

Audit Output Format

When reviewing a user's setup or draft campaign, respond with:

## Deliverability Assessment

### Status: [READY | NEEDS WORK | BLOCKED]

### DNS Authentication
- SPF: [✅ / ⚠️ / ❌] — [detail]
- DKIM: [✅ / ⚠️ / ❌] — [detail]
- DMARC: [✅ / ⚠️ / ❌] — [detail]

### Message Format
- [plain text / HTML / links / images] — [pass or flag]

### Recipient Risk
- ICP environment: [e.g. corporate + likely SEG]
- Notes: [specific risks]

### Required Actions (ordered)
1. ...

Why This Matters

Good deliverability plus relevant messaging lets legitimate offers reach the right person. One inbox placement can start a conversation with real impact — but only if authentication, format, and trust signals are in place first.

Reference

For DNS check commands and SEG notes, see checklist.md.

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.