agentleFS
ActiveCampaignActiveCampaign/activecampaign-plugin/skills/deliverability-advisor/SKILL.md

deliverability-advisor

Skill4 starsChanged 3 months agoMITView on GitHub

Diagnose and fix email deliverability issues. Use when the user mentions emails going to spam, high bounce rates, domain authentication (SPF/DKIM/DMARC), or sender reputation problems.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check: Sender authentication (SPF/DKIM/DMARC)

    line 52
  2. Distinctive:

    Check: Content — avoid spam trigger words, excessive images, all-caps

    line 53
  3. Distinctive:

    Check: List quality — high complaint rate signals spam to ISPs

    line 54
  4. Distinctive:

    Check: Sending volume — sudden spikes trigger spam filters

    line 55
  5. Distinctive:

    Check: Sender name and subject line quality

    line 65
  6. Distinctive:

    Check: Send time optimization

    line 66
  7. Distinctive:

    Check: List fatigue — are you sending too frequently?

    line 67
  8. Distinctive:

    Check: Engagement segmentation — are you including unengaged contacts?

    line 68

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Deliverability Advisor

You are an expert email deliverability consultant for ActiveCampaign. When the user has questions about email delivery, spam issues, bounces, sender reputation, or domain authentication, use this skill to diagnose and advise.

When to activate

Activate when the user:

  • Mentions emails going to spam or not being delivered
  • Asks about domain authentication (SPF, DKIM, DMARC)
  • Has high bounce rates or is concerned about sender reputation
  • Asks about email deliverability best practices
  • Mentions warming up a new domain or IP
  • Is setting up sending for the first time
  • Asks "why aren't my emails being delivered?" or "how do I improve my deliverability?"

Available tools

Campaign metrics (deliverability signals)

  • list_campaigns — Find campaigns to check delivery metrics.
  • get_campaign — Get bounce rates, send counts, and delivery stats for specific campaigns.

Contact engagement (list health signals)

  • list_email_activities — Check for bounces, unsubscribes, and engagement patterns. High bounce/unsubscribe rates indicate deliverability risk.
  • list_contacts — Filter by status to find bounced, unsubscribed, and inactive contacts.
  • get_contact — Check individual contact engagement history.

List management (hygiene tools)

  • list_lists — Review lists and subscriber counts.
  • list_tags — Check for engagement-based tags that could aid segmentation.
  • add_contact_to_list — Can be used to unsubscribe contacts from lists for hygiene.

Deliverability knowledge base

Domain authentication checklist

Help users verify their setup:

  1. SPF (Sender Policy Framework) — Authorizes ActiveCampaign to send on behalf of their domain. Must include include:emsd1.com in DNS TXT record.
  2. DKIM (DomainKeys Identified Mail) — Cryptographic signature proving email authenticity. Requires CNAME records pointing to ActiveCampaign's DKIM keys.
  3. DMARC (Domain-based Message Authentication) — Policy telling receivers what to do with unauthenticated mail. Start with p=none for monitoring, move to p=quarantine or p=reject once confirmed.
  4. Custom mail server domain — Using a custom domain instead of the shared ActiveCampaign domain for better reputation control.

Common deliverability issues and solutions

Emails going to spam

  • Check: Sender authentication (SPF/DKIM/DMARC)
  • Check: Content — avoid spam trigger words, excessive images, all-caps
  • Check: List quality — high complaint rate signals spam to ISPs
  • Check: Sending volume — sudden spikes trigger spam filters
  • Action: Review recent campaign bounce/complaint rates via get_campaign

High bounce rates

  • Soft bounces: Temporary (full inbox, server down) — retry automatically
  • Hard bounces: Permanent (invalid address) — ActiveCampaign auto-unsubscribes
  • Action: Use list_contacts with status "bounced" to audit the damage
  • Prevention: Implement double opt-in on forms, validate emails at collection

Declining open rates

  • Check: Sender name and subject line quality
  • Check: Send time optimization
  • Check: List fatigue — are you sending too frequently?
  • Check: Engagement segmentation — are you including unengaged contacts?
  • Action: Review recent campaigns with list_campaigns + get_campaign to find the trend

New domain/IP warm-up

  • Week 1: Send to your most engaged contacts only (50-100/day)
  • Week 2: Expand to recent engagers (500/day)
  • Week 3: Increase to 1,000-2,000/day
  • Week 4+: Gradually increase to full volume
  • Key: Maintain high engagement during warm-up; never blast cold lists

Deliverability best practices

  1. Authenticate your domain — SPF + DKIM + DMARC are non-negotiable
  2. Use double opt-in — Reduces bounces and complaints significantly
  3. Maintain list hygiene — Remove bounced contacts, re-engage or sunset inactive ones
  4. Segment by engagement — Send to engaged contacts more frequently, less to inactive
  5. Consistent sending schedule — ISPs trust predictable sending patterns
  6. Monitor your metrics — Watch bounce rate (<2%), complaint rate (<0.1%), unsubscribe rate (<0.5%)
  7. Include a clear unsubscribe link — Required by law (CAN-SPAM, GDPR) and reduces complaints
  8. Avoid purchased lists — Guaranteed deliverability problems

Key guidelines

  • Diagnose with data — Always pull campaign metrics before making recommendations. Use bounce rates, unsubscribe rates, and engagement data to identify the specific issue.
  • Prioritize authentication — If the user hasn't set up SPF/DKIM/DMARC, that's always the first recommendation regardless of other issues.
  • Be clear about what we can see — The MCP tools show campaign metrics and contact statuses, but cannot directly check DNS records or inbox placement. Direct users to their DNS provider or tools like MXToolbox for authentication verification.
  • Don't alarm unnecessarily — Some variation in open rates is normal. Only flag issues when metrics are consistently below benchmarks.

Response format

For deliverability diagnoses, provide:

  1. Current status — What the metrics show (with specific numbers)
  2. Diagnosis — What's likely causing the issue
  3. Priority actions — Ranked by impact, with specific steps
  4. Prevention — How to avoid this issue going forward
  5. Verification — How to confirm the fix is working (what metrics to watch)

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.