outreach-deliverability
Skill6 starsChanged 4 days agoApache-2.0View on GitHub
Cold email deliverability: SPF, DKIM, DMARC, sending domains, warmup, volume caps, list hygiene. Use when planning outreach setup or fixing spam placement.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- emelia-io/claude-outreachtheir own version, first seen Sep 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- emelia-io/claude-outreach★ 21same 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 repository145 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ad-bingSkill
- ad-frameworksSkill
- ad-googleSkill
- ad-linkedinSkill
- ad-metaSkill
- ad-redditSkill
- ad-tiktokSkill
- ad-xSkill
- ad-youtubeSkill
- ai-agent-designSkill
- ai-cost-finopsSkill
- ai-evals-designSkill
- ai-prompt-injection-defenseSkill
- ai-rag-patternsSkill
- analytical-reportSkill
- ats-optimizationSkill
- browser-backlink-submissionSkill
- browser-social-account-maintenanceSkill
- chef-budget-mealsSkill
- coaching-frameworksSkill
- code-review-lensesSkill
- code-reviewSkill
- commerce-ai-readinessSkill
- content-auditSkill
- content-formatsSkill
- content-geoSkill
- content-groundingSkill
- content-humanizeSkill
- content-locale-humanize-arSkill
- content-locale-humanize-deSkill
- content-locale-humanize-esSkill
- content-locale-humanize-frSkill
- content-locale-humanize-hiSkill
- content-locale-humanize-itSkill
- content-locale-humanize-jaSkill
- content-locale-humanize-koSkill
- content-locale-humanize-ptSkill
- content-locale-humanizeSkill
- content-locale-humanize-thSkill
- content-locale-humanize-zhSkill
- content-translateSkill
- content-voiceSkill
- cover-letterSkill
- device-computer-automationSkill
- device-mobile-automationSkill
- document-exportSkill
- geo-source-actionsSkill
- geo-visibility-auditSkill
- git-workflowSkill
- issue-diagnosisSkill
- learning-scienceSkill
- marketing-review-programSkill
- marketing-social-gtmSkill
- markup-landing-pageSkill
- octomind-cliSkill
- octomind-configSkill
- octomind-runtimeSkill
- octomind-supervisorSkill
- octomind-workflowSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
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
- Distinctive: line 43
Verify addresses before sending.
- Distinctive: line 44
Remove hard bounces, unsubscribes, and complaints immediately and permanently.
- Distinctive: line 45
No purchased lists and no scraped lists with unclear provenance.
- Distinctive: line 46
Never re-contact someone who opted out, on any domain or sequence.
- Distinctive: line 51
No spam trigger words and no misleading subjects.
- Distinctive: line 64
When mail is not landing, check in this order and change one thing at a time:
- Very specific: line 75
Use the outreach-cold-copy skill for the message itself and the outreach-compliance skill for consent and opt-out rules.
≈ “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.
Files
Overview
Outreach fails silently when mail lands in spam. Deliverability is infrastructure plus behaviour: authenticated sending domains, gradual volume, clean lists, and messages that readers do not mark as spam. This skill specifies the setup and the diagnostic order. It designs and diagnoses; it does not send.
Mailbox-provider rules change. The figures below are the commonly cited working norms; confirm against the current Google, Yahoo, and Microsoft sender guidelines before committing a plan.
Mental model
Mailbox providers score sender reputation from authentication, complaint rate, bounce rate, and engagement. Reputation attaches to the domain and the IP. A cold campaign borrows reputation; a complaint spike spends it. Protect the primary domain by sending outreach from separate domains.
Rules
Infrastructure
- Separate sending domains for outreach, never the primary company domain. Close variants of the brand are common practice.
- Each sending domain has SPF, DKIM, and a DMARC record. Start DMARC at
p=nonewith reporting, aligned with the From domain. - A few mailboxes per domain, each with a real name and signature. Do not spread volume across dozens of throwaway domains.
- Bulk-sender rules: Google applies them at about 5,000 messages a day to personal Gmail accounts, Yahoo to bulk senders without a published number, and Microsoft at 5,000+ a day to Outlook.com since 5 May 2025. All three require SPF and DKIM passing plus an aligned DMARC record.
- Gmail and Yahoo also require one-click unsubscribe on marketing mail, and cold outreach counts: RFC 8058
List-UnsubscribeplusList-Unsubscribe-Post: List-Unsubscribe=One-Click, honoured within 2 days.
Warmup and volume
- Warm new domains 2 to 4 weeks with low, rising volume and real replies before campaign traffic.
- A cap in the region of 30 sends per mailbox per day is a practitioner norm, not a provider rule. Raise it only while metrics stay healthy.
- Sudden volume jumps are a spam signal. Ramp gradually.
Hygiene
- Verify addresses before sending. Target bounces under about 2%.
- Remove hard bounces, unsubscribes, and complaints immediately and permanently.
- No purchased lists and no scraped lists with unclear provenance.
- Never re-contact someone who opted out, on any domain or sequence.
Content
- Plain text, one link, no attachments, no open-tracking pixel on first touch.
- No spam trigger words and no misleading subjects.
- Individual copy: identical bodies at scale are easier to cluster and filter.
Targets and thresholds
| Metric | Working target |
| Spam complaint rate | Under 0.1%, hard ceiling 0.3% |
| Bounce rate | Under about 2% |
| Replies and meetings | The success measure; opens are a diagnostic only |
Diagnostic order
When mail is not landing, check in this order and change one thing at a time:
- Authentication: SPF, DKIM, DMARC pass and align.
- Domain age and warmup state.
- List quality and bounce rate.
- Volume and sending pattern.
- Copy: spam words, links, tracking, length.
- Complaints and blocklists.
Shared rules
Use the outreach-cold-copy skill for the message itself and the outreach-compliance skill for consent and opt-out rules.
Examples
Bad: "Send 500 a day from our main domain starting tomorrow."
Good: "Two new domains, two mailboxes each, SPF/DKIM/DMARC live, 3 weeks warmup, then 20 sends per mailbox per day on a verified list, stopping if complaints pass 0.1%."
Checklist
- Outreach sent from separate domains, not the primary one?
- SPF, DKIM, and DMARC pass and align on each sending domain?
- Warmup of 2 to 4 weeks before campaign traffic?
- Lists verified, bounces under about 2%, opt-outs suppressed permanently?
- Complaint threshold and a kill rule defined?
- Current provider guidelines re-checked rather than relying on this list?
Composition / References
- Pair with
outreach-cold-copyandoutreach-compliance. - This skill covers email only. LinkedIn automation violates its User Agreement; keep those touches manual.
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
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.

