deliverability-check

Audit outbound email deliverability across warmup state, list hygiene, queue caps, and authentication.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/JYeswak/grok_bot_playground --skill deliverability-check-jyeswak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deliverability-check
Source: https://github.com/JYeswak/grok_bot_playground/tree/main/plugin/skills/deliverability-check
Command: npx skills add https://github.com/JYeswak/grok_bot_playground --skill deliverability-check-jyeswak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sending a cold email batch without checking deliverability risks bounces, spam-trap hits, and a burned sending domain. This Skill audits whether an outbound batch is safe to send before any send happens, and blocks the send when the numbers fail. ## Core Features & Use Cases - Warmup and hygiene audit: Checks sending identity age, volume ramp, complaint rate, bounce history, and spam-trap exposure patterns. - Cap-aware queue sizing: Compares planned batch size against per-day and per-domain caps, and reports SPF/DKIM/DMARC posture as present, missing, or unchecked. - Verdict output: Returns per-check PASS/FAIL/WARN with sources, then one verdict: SEND, SEND-CAPPED with the cap, or HOLD with the blocker named. - Use Case: Before launching a cold outreach sequence of 2,000 contacts, run the audit to confirm the sending identity is warmed, bounce rate is acceptable, and the batch fits daily caps. ## Quick Start Ask the assistant to run a deliverability check on the planned outbound batch and report whether it is safe to send.

Frequently Asked Questions about deliverability-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check email deliverability before sending a cold campaign?▼

Run a deliverability audit covering four areas in order: sending identity warmup state, list hygiene and bounce history, per-day and per-domain queue caps, and SPF/DKIM/DMARC authentication. The audit returns a SEND, SEND-CAPPED, or HOLD verdict with the numbers behind each check.

What causes cold email to land in spam?▼

The top failure mode is a cold sending identity paired with a large batch. Other causes include high bounce rates, spam-trap exposure from role addresses or scraped domains, missing SPF/DKIM/DMARC records, and exceeding daily sending caps.

Does this deliverability check send or warm up emails?▼

No. It is a strictly read-only audit that never sends, schedules, warms, cleans, or modifies any list, domain record, or campaign. It only reads metrics and produces a verdict on whether a batch is safe to send.

What happens when a deliverability metric cannot be measured?▼

A metric without a source is recorded as unmeasured rather than invented, and unmeasured metrics fail closed to a HOLD verdict. Authentication records are reported as unchecked when DNS is unreadable, never assumed present.

Can I override a FAIL result and send anyway?▼

A FAIL stops the send by default. Overriding requires an explicit human confirmation on the exact batch in question; the audit itself never proceeds past a HOLD verdict on its own.