agentleFS
MattSezginMattSezgin/unofficial-smartlead-cli/.claude/skills/audit-mailbox-config/SKILL.md

audit-mailbox-config

Skill8 starsChanged 6 months agoMITView on GitHub

Verify a Smartlead mailbox's configuration against the verified golden standard. Checks warmup settings, sending limits, custom tracking domain, signature, client assignment, and tags. Reports drift from best practice. Use when the user asks to audit, validate, verify, or check mailbox settings.

The file

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
  1. Distinctive:

    If empty or wrong, link wrapping and open tracking will fail.

    line 74
  2. Distinctive:

    If audit finds drift and the user wants to fix:

    line 86

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

/audit-mailbox-config

You're checking a mailbox (or batch) against the verified golden config.

What you need from the user

  • One mailbox ID, OR
  • A filter (campaign-id, tag-id, client-id) to audit a batch

How to run it

smartlead accounts get <mailbox_id> --output json

Or for a batch:

smartlead accounts list --client-id <client_id> --output json

The golden config to check against

This config is for Gmail mailboxes. Before auditing, read the mailbox type — if it's not GMAIL, skip the value-specific comparison and only audit structural fields (warmup enabled, signature set, tracking domain set, client_id set).

type: GMAIL
message_per_day: 15
warmup_enabled: true
warmup_details.warmup_min_count: 1
warmup_details.warmup_max_count: 20
warmup_details.daily_rampup: 5
warmup_details.reply_rate: 60
warmup_details.auto_adjust_warmup: false
warmup_details.warmup_key_id: <5+5 format>
warmup_details.send_warmups_only_on_weekdays: true
custom_tracking_domain: emailtracking.<domain>
signature: <not empty>
client_id: <not null if it should have one>

Report format

For each mailbox, produce a table:

FieldExpectedActualStatus
message_per_day1520⚠️ over cap
warmup_min_count115❌ ramp not configured
warmup_max_count2020✅
daily_rampup51⚠️ slow ramp
reply_rate6060✅
client_idnot nullnull❌ orphan
............

CNAME check

Custom tracking domain needs a working CNAME:

TRACKING_DOMAIN=$(smartlead accounts get <mailbox_id> --output json | jq -r '.custom_tracking_domain')
dig +short CNAME "$TRACKING_DOMAIN"

Expected: open.sleadtrack.com. (plus Smartlead's ALB).

If empty or wrong, link wrapping and open tracking will fail.

Common drift patterns to call out

  1. message_per_day: 20 — over the golden cap. Warmup will get squeezed out.
  2. warmup_min_count: 15, warmup_max_count: 20 — happens when warmup was set via the public API with daily_rampup < 5. Fix via the bulk-update endpoint to get warmup_min_count: 1.
  3. client_id: null — orphan mailboxes. Happens when client record was created after mailbox provisioning. Backfill via /bulk-config-mailboxes.
  4. use_custom_domain: true during weeks 1-3 of warmup — risks burning your tracking domain reputation on synthetic warmup traffic. Toggle OFF until mailbox is mature.
  5. Custom tracking CNAME not resolving — usually a Zapmail/Hypertide provisioning gap. Fix at the DNS layer.

Auto-fix offer

If audit finds drift and the user wants to fix:

smartlead accounts bulk-update \
  --ids <ids> \
  --message-per-day 15 \
  --warmup-min 1 \
  --warmup-max 20 \
  --rampup-value 5 \
  --reply-rate 60

(Refer to /warmup-mailboxes skill for the full apply flow.)

Reference

  • docs/learnings/mailbox-warmup-best-practices.md — why these specific numbers
  • docs/learnings/warmup-key-id-format.md — warmup_key_id format rules
  • docs/learnings/bulk-update-endpoint.md — how the bulk-update flow works

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.