email-infra-check
Skill4 starsChanged 8 months agoMITView on GitHub
Audit email sending infrastructure health across client accounts. Use when checking deliverability, before launching campaigns, or during weekly reviews.
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 13
Before launching a new campaign
- Distinctive: line 20
Read the client's campaign folder for active sending domains and accounts.
- Distinctive: line 26
Check each sending account for:
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Email Infrastructure Check
Monitor and audit email sending health for client campaigns.
When to Activate
- User asks to "check email health", "audit deliverability"
- Before launching a new campaign
- Weekly infrastructure review
Process
Step 1: Identify Client Accounts
Read the client's campaign folder for active sending domains and accounts.
Step 2: Run Audit
See AUDIT.md for detailed checks.
Check each sending account for:
- Domain authentication (SPF, DKIM, DMARC)
- Sending volume vs. warming stage
- Bounce rate (flag if > 3%)
- Spam complaint rate (flag if > 0.1%)
- Inbox placement estimate
Step 3: Report
Generate a health scorecard:
| Account | Domain Auth | Volume | Bounce Rate | Status |
| account-1@send.client.com | Pass | 45/day | 1.2% | Healthy |
| account-2@send.client.com | Fail DMARC | 30/day | 4.1% | Warning |
Step 4: Recommendations
For any flagged issues, provide:
- What's wrong
- How to fix it
- Priority (critical / warning / info)
Related Skills
- outbound-report - Include infrastructure health in weekly reports
In this repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- buyer-tieringSkill
- campaign-strategySkill
- list-builderSkill
- outbound-reportSkill
- proposal-builderSkill
- prospect-researchSkill
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.