Agent skill
deliverability-test-public
Compare reply rates, bounce rates, and positive reply rates broken down by inbox type (SMTP / Gmail / Outlook) for a Smartlead account.
Filed under Outbound email.
From growthenginenowoslawski/coldoutboundskills · 50 skills · 668 · pushed 2026-08-18
What it does when it runs
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).
Read from the skill and the 1 file bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- API_KEY
- SMARTLEAD_API_KEY
- Hosts it reaches
- server.smartlead.ai
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It does act, so it runs under whatever permissions your session already grants. - Actions present in the files
- shellnetwork
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/growthenginenowoslawski/coldoutboundskills.git /tmp/coldoutboundskills git -C /tmp/coldoutboundskills sparse-checkout set "skills/deliverability-test-public" mkdir -p ~/.claude/skills/deliverability-test-public cp -R "/tmp/coldoutboundskills/skills/deliverability-test-public/." ~/.claude/skills/deliverability-test-public/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
Before you install: this skill will not complete its job on a bare agent. It needs API_KEY, SMARTLEAD_API_KEY, which you have to obtain separately.
The skill
Source on GitHub ↗Reproduced in full from growthenginenowoslawski/coldoutboundskills/blob/f24320d4ab3ddb717402a065a3679aca5a7a8665/skills/deliverability-test-public/SKILL.md, which is licensed MIT (repository). 515 words, 13 headings.
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=1
Output
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
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- public-relations by coreyhaines31 · 46,928
- ab-test-setup by OpenClaudia · 677
- ab-test-setup by louisblythe · 143
- message-deliverability-optimization by louisblythe · 143
- ab-test-setup by manojbajaj95 · 95
- cold-email-deliverability by bcharleson · 6
- ab-test-analyzer by ekatasingh1107 · 2
Need help setting it up?
This page tells you what deliverability-test-public does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.