Agent skill

Deliverability Test Public

by growthenginenowoslawski in growthenginenowoslawski/coldoutboundskills

Compare reply rates, bounce rates, and positive reply rates broken down by inbox type (SMTP / Gmail / Outlook) for a Smartlead account.

MITAuto-check passedBackend & APIs

Install Deliverability Test Public

skills CLI

$ npx skills add growthenginenowoslawski/coldoutboundskills --skill deliverability-test-public -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install growthenginenowoslawski/coldoutboundskills deliverability-test-public --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/growthenginenowoslawski/coldoutboundskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/deliverability-test-public .claude/skills/deliverability-test-public && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "deliverability-test-public" agent skill from https://github.com/growthenginenowoslawski/coldoutboundskills/tree/main/skills/deliverability-test-public into .claude/skills/deliverability-test-public/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deliverability-test-public", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/growthenginenowoslawski/coldoutboundskills/tree/main/skills/deliverability-test-public

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add growthenginenowoslawski/coldoutboundskills --skill deliverability-test-public -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install growthenginenowoslawski/coldoutboundskills deliverability-test-public --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/growthenginenowoslawski/coldoutboundskills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/deliverability-test-public .agents/skills/deliverability-test-public && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "deliverability-test-public" agent skill from https://github.com/growthenginenowoslawski/coldoutboundskills/tree/main/skills/deliverability-test-public into .agents/skills/deliverability-test-public/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deliverability-test-public", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add growthenginenowoslawski/coldoutboundskills --skill deliverability-test-public -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install growthenginenowoslawski/coldoutboundskills deliverability-test-public --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/growthenginenowoslawski/coldoutboundskills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/deliverability-test-public .cursor/skills/deliverability-test-public && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "deliverability-test-public" agent skill from https://github.com/growthenginenowoslawski/coldoutboundskills/tree/main/skills/deliverability-test-public into .cursor/skills/deliverability-test-public/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deliverability-test-public", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/growthenginenowoslawski/coldoutboundskills.git --path skills/deliverability-test-public

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add growthenginenowoslawski/coldoutboundskills --skill deliverability-test-public -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install growthenginenowoslawski/coldoutboundskills deliverability-test-public --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/growthenginenowoslawski/coldoutboundskills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/deliverability-test-public .gemini/skills/deliverability-test-public && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "deliverability-test-public" agent skill from https://github.com/growthenginenowoslawski/coldoutboundskills/tree/main/skills/deliverability-test-public into .gemini/skills/deliverability-test-public/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deliverability-test-public", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install growthenginenowoslawski/coldoutboundskills deliverability-test-public

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add growthenginenowoslawski/coldoutboundskills --skill deliverability-test-public -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/growthenginenowoslawski/coldoutboundskills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/deliverability-test-public .github/skills/deliverability-test-public && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "deliverability-test-public" agent skill from https://github.com/growthenginenowoslawski/coldoutboundskills/tree/main/skills/deliverability-test-public into .github/skills/deliverability-test-public/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deliverability-test-public", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add growthenginenowoslawski/coldoutboundskills --skill deliverability-test-public -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install growthenginenowoslawski/coldoutboundskills deliverability-test-public --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/growthenginenowoslawski/coldoutboundskills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/deliverability-test-public .opencode/skills/deliverability-test-public && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "deliverability-test-public" agent skill from https://github.com/growthenginenowoslawski/coldoutboundskills/tree/main/skills/deliverability-test-public into .opencode/skills/deliverability-test-public/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deliverability-test-public", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: deliverability-test-public
GitHub stars: 753
Token cost: ~1k tokens
SKILL.md length: 347 words
Files: 2 (incl. scripts)
Skills in repo: 49
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Compare reply rates, bounce rates, and positive reply rates broken down by inbox type (SMTP / Gmail / Outlook) for a Smartlead account.

Works in 5 steps: Pulls all email accounts via… → Groups by type field (GMAIL, OUTLOOK,… → For each campaign that uses these… → …
You want to know which inbox type delivers best
SKILL.md covers Why this exists, What you need, Steps and Output, plus 5 more sections
Runs TypeScript scripts from its folder; calls npx; needs SMARTLEAD_API_KEY

What it does

Deliverability Test Public is an agent skill from growthenginenowoslawski/coldoutboundskills. 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).

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/inbox-type-compare.ts`).

It sits in Backend & APIs, covering Transactional email and Email management. It works with Gmail. The repository describes itself as: Open-source Claude Code skills for cold email and outbound sales. Grade campaigns, export Prospeo searches, scrape Google Maps — all from Claude Code. The licence is MIT.

When your agent uses it

You want to know which inbox type delivers best
Debugging unexplained deliverability differences across a mixed fleet

Example prompts

“which inbox type delivers best”
“/deliverability-test-public”

Requirements

Node.js
A credential in SMARTLEAD_API_KEY

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Pulls all email accounts via /email-accounts API paginated
Groups by type field (GMAIL, OUTLOOK, SMTP, etc.)
For each campaign that uses these inboxes, pulls per-inbox stats from /campaigns/{id}/analytics and…
Aggregates sent/replies/bounces within each type group
Prints formatted table

What it can do on your machine

Read from SKILL.md and the folder at commit 25c5d85. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (TypeScript), which the agent can run.
Shell commands in SKILL.md call:
- npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- SMARTLEAD_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Deliverability Test Public loads about 1k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 347 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~89
When it runs · the whole SKILL.md, loaded when a task matches: ~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from growthenginenowoslawski/coldoutboundskills at commit 25c5d85, republished under its MIT licence (© growthenginenowoslawski). 347 words, ~1,020 tokens.

Download SKILL.mdSave it as .claude/skills/deliverability-test-public/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: deliverability-test-public
description: 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).

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_KEY in env
Optional: --client-id=<id> for sub-clients
Optional: --days=<N> lookback (default 7)

Steps

bash

# 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-accounts API paginated
Groups by type field (GMAIL, OUTLOOK, SMTP, etc.)
For each campaign that uses these inboxes, pulls per-inbox stats from /campaigns/{id}/analytics and /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.

/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

SKILL.md and 1 other file (scripts) in skills/deliverability-test-public of growthenginenowoslawski/coldoutboundskills.

SKILL.md
scripts/inbox-type-compare.ts

Open the folder on GitHubat commit 25c5d85

Compare with similar skills

Deliverability Test Public next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Deliverability Test Public compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Deliverability Test Public this skillgrowthenginenowoslawski/coldoutboundskills	753	—	~1k	Automated safety check: Pass	MIT	5 days ago
Smtp Email Senderopenakita/openakita	2k	—	~693	Automated safety check: Notes	AGPL-3.0	17 days ago
Google Workspaceericrisco/rsc-harness	180	—	~3.2k	Automated safety check: Pass	MIT	yesterday
Email Deliverabilityericrisco/rsc-harness	180	—	~2.3k	Automated safety check: Pass	MIT	yesterday
Imap Smtp Emailfreestylefly/wesight	946	3 repos	~1.7k	Automated safety check: Notes	MIT	9 days ago
Mjml Email TemplatesAaronontheweb/dotnet-skills	1.2k	1 repos	~2.7k	Automated safety check: Pass	MIT	today

Similar skills

Smtp Email Sender
openakita/openakita
Send emails via SMTP (Gmail, Outlook, etc.). An agent skill from openakita/openakita.
2k GitHub stars~693 tokensUpdated 17 days ago
Backend & APIsAuto-check: notes
Google Workspace
ericrisco/rsc-harness
A skill your agent uses when server-side code reads or writes Gmail, Drive, Calendar, or Sheets with a GCP service account and no human in the OAuth loop: picking the auth mode (app-owned vs…
180 GitHub stars~3.2k tokensUpdated yesterday
Backend & APIsAuto-check passed
Email Deliverability
ericrisco/rsc-harness
A skill your agent uses when mail already sent lands in spam, is rejected, or fails the Gmail/Yahoo bulk-sender checks and the fix is authentication and reputation, not the sending code…
180 GitHub stars~2.3k tokensUpdated yesterday
Backend & APIsAuto-check passed
Imap Smtp Email
freestylefly/wesight
Read and send email via IMAP/SMTP. An agent skill from freestylefly/wesight.
946 GitHub starsUsed in 3 repos~1.7k tokens
Backend & APIsAuto-check: notes
Mjml Email Templates
Aaronontheweb/dotnet-skills
Build responsive email templates using MJML markup language.
1.2k GitHub starsUsed in 1 repo~2.7k tokens
Backend & APIsAuto-check passed
Imap Smtp Email
wentorai/Research-Claw
Read, search, and manage email via IMAP protocol. An agent skill from wentorai/Research-Claw.
858 GitHub stars~1.3k tokensUpdated 1 mo ago
Backend & APIsAuto-check: notes

Questions about Deliverability Test Public

What does Deliverability Test Public do?

Compare reply rates, bounce rates, and positive reply rates broken down by inbox type (SMTP / Gmail / Outlook) for a Smartlead account. Deliverability Test Public is an agent skill from growthenginenowoslawski/coldoutboundskills. Compare reply rates, bounce rates, and positive reply rates broken down by inbox type (SMTP / Gmail / Outlook) for a Smartlead account.

When should I use Deliverability Test Public?

Deliverability Test Public fits situations like: you want to know which inbox type delivers best; debugging unexplained deliverability differences across a mixed fleet.

How do I install Deliverability Test Public in Claude Code?

Run `npx skills add growthenginenowoslawski/coldoutboundskills --skill deliverability-test-public -a claude-code`. Or copy the skill folder (skills/deliverability-test-public in growthenginenowoslawski/coldoutboundskills) into .claude/skills/deliverability-test-public in your project. Claude Code loads it when a task matches its description.

How do I install Deliverability Test Public in Codex?

Run `npx skills add growthenginenowoslawski/coldoutboundskills --skill deliverability-test-public -a codex`. Or copy the skill folder (skills/deliverability-test-public in growthenginenowoslawski/coldoutboundskills) into .agents/skills/deliverability-test-public in your project. Codex loads it when a task matches its description.

Can I use Deliverability Test Public in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add growthenginenowoslawski/coldoutboundskills --skill deliverability-test-public -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deliverability-test-public, .gemini/skills/deliverability-test-public, .github/skills/deliverability-test-public and .opencode/skills/deliverability-test-public in your project.

What does Deliverability Test Public need to run?

Going by SKILL.md and its folder, Deliverability Test Public needs TypeScript for the scripts in its folder, the command-line tools its instructions call (npx) and credentials named SMARTLEAD_API_KEY. Our summary lists: Node.js; A credential in SMARTLEAD_API_KEY.

Does Deliverability Test Public access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Deliverability Test Public safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Deliverability Test Public use?

Deliverability Test Public is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Deliverability Test Public use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Deliverability Test Public?

Skills that share tags, products or a category with Deliverability Test Public: Smtp Email Sender (openakita/openakita, 2k stars), Google Workspace (ericrisco/rsc-harness, 180 stars), Email Deliverability (ericrisco/rsc-harness, 180 stars) and Imap Smtp Email (freestylefly/wesight, 946 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Deliverability Test Public?

growthenginenowoslawski (a GitHub user) maintains it in growthenginenowoslawski/coldoutboundskills, which has 753 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 5, 2026.

Source: growthenginenowoslawski/coldoutboundskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Deliverability Test Public

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Deliverability Test — Inbox Type Comparison

Why this exists

What you need

Steps

Output

How it works

Common gotchas

What to do next

Related skills

Scripts

Files

Compare with similar skills

Similar skills

More from growthenginenowoslawski/coldoutboundskills

Related

Questions about Deliverability Test Public