本文へ移動
cccskills
無料GitHub で公開

deliverability-test-public

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).

インストール方法を見る

含まれるファイル(2)

  • SKILL.md4.0 KB
  • scripts/inbox-type-compare.ts7.2 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

# 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

  1. Pulls all email accounts via /email-accounts API paginated
  2. Groups by type field (GMAIL, OUTLOOK, SMTP, etc.)
  3. For each campaign that uses these inboxes, pulls per-inbox stats from /campaigns/{id}/analytics and /campaigns/{id}/sequence-analytics-by-email-account
  4. Aggregates sent/replies/bounces within each type group
  5. 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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Autonomous cold email campaign launcher. Takes one target company domain, scrapes their website, generates an ICP with Claude, pulls matching leads via Prospeo, enriches emails + company descriptions, personalizes each lead with parallel Claude Code Task sub-agents (A/B/C variants), and uploads as a live Smartlead campaign. Uses local JSON files for state (no database required). Use for automated daily campaign launches after you have an initial `client-profile.yaml` from /icp-onboarding. Triggers on "auto-research", "launch an automated campaign", "daily campaign", "run the research loop".

日本語の概要は準備中です。原文の説明を表示しています。

growthenginenowoslawski/coldoutboundskills7602026年10月6日 更新

Use the Blitz API to find decision-makers at specific companies when you already have a list of company domains. Best for SMB owner-finding, domain-to-people lookup, or supplementing Prospeo results. Outputs a CSV you can feed to the /list-builder Phase 5 or directly to /cold-email-starter-kit for Smartlead upload. Use when your targeting is company-first (not title-first).

日本語の概要は準備中です。原文の説明を表示しています。

growthenginenowoslawski/coldoutboundskills7602026年10月6日 更新

Creates cold email copy through a stepwise confirmation process. Use when writing email campaigns, given a campaign strategy document, website, or client context. Confirms direction at each step before outputting final copy.

日本語の概要は準備中です。原文の説明を表示しています。

growthenginenowoslawski/coldoutboundskills7602026年10月6日 更新

Generates 15-25+ cold outbound campaign ideas with targeting strategies, AI personalization approaches, and value propositions. Use when planning campaign experiments for a client, given their website or business context.

日本語の概要は準備中です。原文の説明を表示しています。

growthenginenowoslawski/coldoutboundskills7602026年10月6日 更新

Index and shared harness for the 19 signal playbooks. Each playbook turns one buying signal (new in role, raised a round, hiring surge, pricing page, tech on website, ...) into one copy-ready sentence you can drop into a cold email. Every playbook ships three ways to run it: as a Claude skill, as a Clay table built through a browser harness, and as a Clay workflow built from the clay CLI. Use when someone says "personalize this list", "what signal should I use", "build the Clay column for X", or names any of the 19 signals.

日本語の概要は準備中です。原文の説明を表示しています。

growthenginenowoslawski/coldoutboundskills7602026年10月6日 更新

Single "start here" orchestrator for new cold email operators. Asks infrastructure-status questions first, then runs /icp-onboarding → /lead-magnet-brainstorm → /campaign-strategy in sequence, producing a consolidated campaign-plan.md. Ends with an interactive menu of next skills branched on whether the user already has domains/inboxes. Use as the very first invocation on any new repo checkout or when onboarding someone to cold email from zero.

日本語の概要は準備中です。原文の説明を表示しています。

growthenginenowoslawski/coldoutboundskills7602026年10月6日 更新

growthenginenowoslawski のスキルをすべて見る

このスキルの問題を報告する