deliverability-test-public
Skill759 starsChanged 28 days agoMITView on GitHub
Compare reply rates, bounce rates, and positive reply rates broken down by inbox type (SMTP / Gmail / Outlook) for a Smartlead account. Use when you want to know "which inbox type delivers best" or when debugging unexplained deliverability differences across a mixed fleet. Operates via Smartlead API only (no database required).
- Reads credentials
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 17
If your campaigns mix inbox types, this skill shows which type is earning its keep.
- Distinctive: line 68
Small inbox counts are noisy: If you only have 2 Gmail inboxes and 40 SMTP ones, the Gmail numbers aren't statistically meaningful.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Deliverability Test — Inbox Type Comparison
Compare reply rates, bounce rates, and positive reply rates broken down by inbox type (SMTP, Gmail / G Suite, Outlook / Office365) across your Smartlead account. Use it to answer "are my Gmail inboxes performing better than my SMTP ones?" or "why is one inbox type bouncing more than the others?"
Why this exists
Different inbox types have different deliverability characteristics:
- Gmail / G Suite — highest trust, fewest bounces, often best reply rates
- Office365 — good reputation, but stricter spam filtering
- SMTP (Zapmail, Maildoso, Mailforge, custom) — varies wildly by provider, often has higher bounces in the first 30 days of domain life
If your campaigns mix inbox types, this skill shows which type is earning its keep.
What you need
SMARTLEAD_API_KEYin env- Optional:
--client-id=<id>for sub-clients - Optional:
--days=<N>lookback (default 7)
Steps
# Full account, last 7 days
npx tsx scripts/inbox-type-compare.ts
# Specific sub-client, 14-day lookback
npx tsx scripts/inbox-type-compare.ts --client-id=5560 --days=14
# Just show today
npx tsx scripts/inbox-type-compare.ts --days=1Output
Inbox Type Comparison — last 7 days
Type Inboxes Sent Replies Bounces Reply % Bounce %
--------------- ------ ------- ------- ------- ------- --------
G Suite 12 3,120 42 12 1.35% 0.38%
Office365 24 6,440 65 28 1.01% 0.43%
SMTP 44 10,780 55 98 0.51% 0.91%
--------------- ------ ------- ------- ------- ------- --------
TOTAL 80 20,340 162 138 0.80% 0.68%
Takeaways:
- G Suite has the highest reply rate (1.35%) and lowest bounce rate.
- SMTP reply rate is 60% lower than G Suite — investigate domain reputation.
- SMTP bounce rate is 2x average — run /email-deliverability-audit on SMTP domains.How it works
- Pulls all email accounts via
/email-accountsAPI paginated - Groups by
typefield (GMAIL, OUTLOOK, SMTP, etc.) - For each campaign that uses these inboxes, pulls per-inbox stats from
/campaigns/{id}/analyticsand/campaigns/{id}/sequence-analytics-by-email-account - Aggregates sent/replies/bounces within each type group
- Prints formatted table
Common gotchas
- Reply rate here is RAW, not positive. For positive reply rate (the more important metric), use
/positive-reply-scoring. - Small inbox counts are noisy. If you only have 2 Gmail inboxes and 40 SMTP ones, the Gmail numbers aren't statistically meaningful.
- Inbox type labels can be surprising. Some providers register as "SMTP" even when they're technically Gmail-proxied. Trust the label Smartlead gave them.
What to do next
If one inbox type is underperforming: /smartlead-inbox-manager to retire the bad ones (tag retired, disable warmup). If replacements are needed, /zapmail-domain-setup-public to provision new domains on a different provider type.
If all types are healthy: back to the weekly rhythm via /cold-email-weekly-rhythm.
Or wait: small sample sizes (<500 sends per type) are noisy. If your results are inconclusive, run again in 7 days with more data.
Related skills
/email-deliverability-audit— full audit (SPF/DKIM/DMARC + reputation + spam placement)/positive-reply-scoring— the metric that matters, not just reply rate/smartlead-inbox-manager— rotate out bad inboxes, tag by performance
Scripts
scripts/inbox-type-compare.ts— pulls + compares per-type rates
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- automatewithuday/GTM-Skills★ 177% same
Wrote their own version · 0
None found.
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 repository51 other files it gives its agents.
- auto-research-publicSkill
- blitz-list-builderSkill
- campaign-copywritingSkill
- campaign-strategySkill
- cold-email-kickoffSkill
- cold-email-starter-kitSkill
- cold-email-weekly-rhythmSkill
- competitor-engagersSkill
- deliverability-incident-responseSkill
- disco-likeSkill
- email-deliverability-auditSkill
- experiment-designSkill
- google-maps-list-builderSkill
- icp-onboardingSkill
- icp-prompt-builderSkill
- inbox-lifecycle-managerSkill
- lead-magnet-brainstormSkill
- list-builderSkill
- list-expanderSkill
- list-quality-scorecardSkill
- perfect-company-listSkill
- personalization-subagent-patternSkill
- clay-playbooksSkill
- playbook-ad-librarySkill
- playbook-ai-specificitySkill
- playbook-case-study-pageSkill
- playbook-company-name-cleaningSkill
- playbook-creative-ideasSkill
- playbook-first-name-cleaningSkill
- playbook-fundraisingSkill
- playbook-google-site-searchSkill
- playbook-hiring-surgeSkill
- playbook-job-posting-languageSkill
- playbook-linkedin-engagementSkill
- playbook-lookalikesSkill
- playbook-name-to-other-prospectsSkill
- playbook-new-in-roleSkill
- playbook-pricing-pageSkill
- playbook-social-link-findingSkill
- playbook-social-postsSkill
- playbook-tech-on-websiteSkill
- playbook-warm-introsSkill
- positive-reply-scoringSkill
- prospeo-full-exportSkill
- prospeo-search-apiSkill
- smartlead-apiSkill
- smartlead-campaign-upload-publicSkill
- smartlead-inbox-managerSkill
- smartlead-spintaxSkill
- spam-word-checkerSkill
- zapmail-domain-setup-publicSkill
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.

