checking-email-deliverability
Skill0 starsChanged 9 days agoMITView on GitHub
Diagnoses why Sendly mail is not landing and fixes the sending setup: domain health, DKIM, SPF, and DMARC records, sending-domain verification, suppressions, and address validation or list cleaning. Use when the user asks 'why is mail from my domain not landing', 'why do my emails go to spam', 'why are emails bouncing', 'what DNS records do I need for DKIM', 'verify my sending domain', 'who is suppressed', or 'clean this list before I send'. Changes are confirmed first.
In this repository66 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adding-uptime-monitorsSkill
- analyzing-page-performanceSkill
- booking-meetingsSkill
- building-onboarding-workflowsSkill
- building-study-guidesSkill
- capturing-tasksSkill
- capturing-web-pagesSkill
- chasing-unpaid-invoicesSkill
- checking-domain-connectionsSkill
- checking-notification-deliverySkill
- checking-uptime-statusSkill
- cleaning-up-bookkeepingSkill
- connecting-customer-domainsSkill
- discussing-buildsSkill
- drafting-invoicesSkill
- drafting-social-postsSkill
- editing-demosSkill
- editing-page-draftsSkill
- extracting-document-textSkill
- finding-meeting-timesSkill
- handling-flaky-changesSkill
- investigating-tasksSkill
- making-demo-videosSkill
- managing-bookingsSkill
- managing-content-calendarSkill
- managing-demosSkill
- managing-voice-librarySkill
- planning-revisionSkill
- preflighting-domainsSkill
- publishing-pagesSkill
- reading-financial-reportsSkill
- reading-text-aloudSkill
- reading-web-pagesSkill
- reporting-snapvisor-usageSkill
- researching-course-materialSkill
- researching-summary-librarySkill
- responding-to-incidentsSkill
- reviewing-email-performanceSkill
- reviewing-notification-workflowsSkill
- reviewing-social-performanceSkill
- reviewing-visual-buildsSkill
- reviewing-workloadSkill
- searching-getitdone-api-docsSkill
- sending-email-campaignsSkill
- sending-notificationsSkill
- setup-bioflowSkill
- setup-calySkill
- setup-demofySkill
- setup-dodomainSkill
- setup-getitdoneSkill
- setup-notiflySkill
- setup-postifySkill
- setup-sendlySkill
- setup-shortySkill
- setup-snapvisorSkill
- setup-superbooksSkill
- setup-unotesSkill
- setup-upapiSkill
- setup-uptimelySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 0 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Every tool in this skill comes from the sendly MCP server, the Sendly connector, and is written here as sendly:<tool>.
- Very specific: line 15
Tools listed by name: call them directly, for example sendly:list_contacts.
- Very specific: line 30
Call sendly:check_domain and report each domain's DKIM, SPF, and DMARC state.
- Very specific: line 32
If DNS records are missing, say which domain you will set up, get a yes, then call sendly:start_domain_setup (or sendly:add_domain first …
- Very specific: line 33
After the user says the records are published, call sendly:verify_domain and report the result.
- Very specific: line 34
If bounces are the issue, call sendly:list_suppressions and show how many addresses are suppressed and why.
- Very specific: line 39
Call sendly:add_domain, sendly:start_domain_setup, or sendly:add_suppression only after the user confirms the exact domain or address.
- Very specific: line 42
Do not tell the user a domain is fixed until sendly:verify_domain or sendly:check_domain says so.
- Very specific: line 43
Do not send email from this skill: never call sendly:send_email, sendly:send_test_email, sendly:send_campaign, or sendly:send_mailbox_email.
≈ “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.
Files
<!-- Generated from plugins/sendly/skills/checking-email-deliverability/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->Sendly deliverability check
Find out why mail from a domain is not landing, walk the user through the fix, and check address quality. Changes to domains and suppressions happen only after the user confirms.
Connecting and calling the tools
Every tool in this skill comes from the sendly MCP server, the Sendly connector, and is written here as sendly:<tool>.
- Tools listed by name: call them directly, for example
sendly:list_contacts. - Only
sendly:search_toolsandsendly:execute_typescriptlisted (Code Mode, the default): callsendly:search_toolsfirst, then call each tool insidesendly:execute_typescriptasexternal_<tool>(for exampleexternal_list_contacts); the program mustreturnits result. Scopes, confirmations and gates are identical on both surfaces. - "Tool not found": switch to the Code Mode route instead of retrying the direct call. If
sendly:search_toolsdoes not return the tool either, its OAuth scope was not granted; the user reconnects Sendly and approves that scope. - No
sendlytools at all: Sendly is not connected yet. Follow thesetup-sendlyskill.
Tools you will use
sendly:check_domain: the project's sending domains with DKIM, SPF, and DMARC status.sendly:diagnose_delivery: an explanation of a domain's delivery health from its DNS state plus recent bounces and suppressions.sendly:add_domain,sendly:start_domain_setup,sendly:verify_domain: add a sending domain, get the DNS records to publish, and check them.sendly:list_suppressions,sendly:add_suppression,sendly:remove_suppression: the addresses mail will not go to, and changes to that list.sendly:validate_emails,sendly:get_validation_run,sendly:list_validation_results,sendly:clean_list: check addresses before sending. Metered per address on the Sendly plan.
Workflow
- Call
sendly:check_domainand report each domain's DKIM, SPF, and DMARC state. - For the domain the user cares about, call
sendly:diagnose_deliveryand summarize the cause it found. - If DNS records are missing, say which domain you will set up, get a yes, then call
sendly:start_domain_setup(orsendly:add_domainfirst for a new domain). List the records to publish, one per line with type, name, and value. - After the user says the records are published, call
sendly:verify_domainand report the result. DNS can take time to propagate; if it fails, name the records still missing. - If bounces are the issue, call
sendly:list_suppressionsand show how many addresses are suppressed and why. - For a list the user wants to check before sending, state the number of addresses and that validation is metered, get a yes, then call
sendly:validate_emailsorsendly:clean_list. Read results withsendly:get_validation_runandsendly:list_validation_results.
Rules
- Call
sendly:add_domain,sendly:start_domain_setup, orsendly:add_suppressiononly after the user confirms the exact domain or address. - Suppressions are the consent record. Call
sendly:remove_suppressiononly when the user says the address owner asked to receive mail again, and confirm the exact address first. - Confirm the address count before any validation or list cleaning, because it is billed per address.
- Do not tell the user a domain is fixed until
sendly:verify_domainorsendly:check_domainsays so. - Do not send email from this skill: never call
sendly:send_email,sendly:send_test_email,sendly:send_campaign, orsendly:send_mailbox_email.
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
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.

