agentleFS
MattSezginMattSezgin/unofficial-smartlead-cli/.claude/skills/check-deliverability/SKILL.md

check-deliverability

Skill8 starsChanged 6 months agoMITView on GitHub

Audit deliverability health of a Smartlead campaign or mailbox pool — bounce rate, reply rate, ESP routing, mailbox warmup status, custom tracking domain validation. Use when the user reports "bounces are high", "campaign is underperforming", "emails are landing in spam", or asks for a deliverability check / audit.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 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.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Look for outliers — one mailbox bouncing at 20% while others are at 2% means that mailbox is cooked.

    line 36
  2. Distinctive:

    If the campaign has both Gmail and Outlook senders:

    line 40
  3. Very specific:

    If true, this is likely tanking Big Tech / Google Workspace recipient bounces.

    line 46
  4. Very specific:

    Should resolve to open.sleadtrack.com.

    line 72
  5. Very specific:

    If google.com, meta.com, figma.com, microsoft.com dominate the bounce list, the issue is likely email-finder false positives (Big Tech …

    line 83

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Before running: verify exact flag names with smartlead <command> --help. Flag shapes shown below are illustrative — confirm against the actual CLI.

/check-deliverability

You're auditing deliverability health to find what's tanking inbox placement.

What you need from the user

  • Scope — one campaign, one mailbox, or a whole client?
  • Symptom — bounces, replies, spam complaints, or just "feels off"?

Audit checklist (run these in order)

1. Campaign-level analytics

smartlead campaigns analytics <campaign_id> --output json

Look for:

  • Bounce rate >5% → red flag
  • Reply rate <1% → check copy + audience
  • Open rate <30% → check inbox placement (but unreliable post Apple Mail Privacy)

2. Per-mailbox health

smartlead analytics email-wise-health --campaign-id <campaign_id> --output table

Look for outliers — one mailbox bouncing at 20% while others are at 2% means that mailbox is cooked.

3. ESP routing check

If the campaign has both Gmail and Outlook senders:

smartlead campaigns get <campaign_id> --output json | jq '.settings.enable_ai_esp_matching'

If true, this is likely tanking Big Tech / Google Workspace recipient bounces. See docs/learnings/esp-matching-analysis.md — the AI ESP matching routes Google recipients to Outlook senders ~90% of the time, costing +11pp bounce rate.

Recommend disabling:

smartlead campaigns settings <campaign_id> --no-ai-esp-matching

4. Mailbox warmup status

smartlead accounts list --campaign-id <campaign_id> --output json \
  | jq '.[] | {id, email, warmup_details: .warmup_details}'

For each mailbox check:

  • warmup_enabled: true
  • total_warmup_per_day between 15-25 (golden config)
  • warmup_reputation > 95%

5. Custom tracking domain CNAME check

# For each mailbox's custom_tracking_domain:
dig CNAME emailtracking.<their-domain>

Should resolve to open.sleadtrack.com. plus a Smartlead ALB. If it doesn't, tracking links and pixels will fail in flight.

6. Big Tech bounce concentration

smartlead leads list <campaign_id> --status BOUNCED --output json \
  | jq '.[] | .email' \
  | awk -F@ '{print $2}' \
  | sort | uniq -c | sort -rn | head -10

If google.com, meta.com, figma.com, microsoft.com dominate the bounce list, the issue is likely email-finder false positives (Big Tech accept-all SMTP confuses verifiers). See docs/learnings/esp-matching-analysis.md.

Common diagnoses

PatternLikely causeFix
High bounce on Google Workspace recipientsAI ESP matching routing to Outlook sendersDisable enable_ai_esp_matching, pair senders explicitly
High bounce on Big Tech (@google.com etc.)Email-finder catch-all guessesSkip Big Tech leads OR use verified-only providers (Findymail, BetterContact)
One mailbox bouncing way more than peersMailbox-specific reputation issuePause that mailbox, audit warmup/auth (SPF/DKIM/DMARC)
Replies near zero across all mailboxesCopy issue, not deliverabilityDifferent problem — don't waste time on infra
Invalid numeric literal at line 1 errors mid-scriptRate limit (~200 sequential GETs)Throttle, batch, or use paginated list endpoints

Output

Summarize for the user:

  1. Top finding (the one thing to fix first)
  2. Supporting evidence (specific numbers from the audit)
  3. Recommended action
  4. (Optional) Other findings ranked by impact

Reference

  • docs/learnings/esp-matching-analysis.md — why AI ESP matching hurts Google bounces
  • docs/learnings/mailbox-warmup-best-practices.md — golden config for healthy mailboxes
  • docs/learnings/rate-limits.md — the HTML-response rate limit

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.