Agent skill

Email Audit

by AgriciDaniel in AgriciDaniel/claude-email

Audits email domain deliverability setup (SPF, DKIM, DMARC, MX records, blacklists, TLS) and generates health score (0-100) with prioritized fix list.

MITAuto-check: notesBackend & APIs

Install Email Audit

skills CLI
$ npx skills add AgriciDaniel/claude-email --skill email-audit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AgriciDaniel/claude-email email-audit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-email.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/email-audit .claude/skills/email-audit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
email-audit
GitHub stars
130
Token cost
~3k tokens
SKILL.md length
1,223 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Audits email domain deliverability setup (SPF, DKIM, DMARC, MX records, blacklists, TLS) and generates health score (0-100) with prioritized fix list.

  • Works in 12 steps: SPF Record (Weight: 10%) → DKIM Record (Weight: 15%) → DMARC Policy (Weight: 15%) → …
  • User asks to audit
  • SKILL.md covers Purpose, Input, Audit Categories and Health Score Calculation, plus 7 more sections
  • Calls python, openssl and curl

What it does

Email Audit is an agent skill from AgriciDaniel/claude-email. Audits email domain deliverability setup (SPF, DKIM, DMARC, MX records, blacklists, TLS) and generates health score (0-100) with prioritized fix list. Checks bulk sender compliance against Google/Yahoo/Microsoft 2024-2026 requirements. Provides DNS records to add/update. Use when user asks to audit, check, or analyze email deliverability, domain health, or inbox placement.

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering Transactional email, Customer success and Email management. The repository describes itself as: AI-powered email management and marketing skill for Claude Code. Inbox triage, composition, quality review, deliverability audit, automation sequences, and marketing strategy. The licence is MIT.

When your agent uses it

  • User asks to audit
  • Analyze email deliverability
  • Inbox placement

Example prompts

  • “Use the email-audit skill to audit email domain deliverability setup (SPF, DKIM, DMARC, MX records, blacklists, TLS) and generates health score…”
  • “/email-audit”

Requirements

  • Python 3
  • Pre-approved tools (allowed-tools): Read, Bash, Grep, Glob

Workflow steps

12 steps, taken from the step headings in SKILL.md.

  1. SPF Record (Weight: 10%)
  2. DKIM Record (Weight: 15%)
  3. DMARC Policy (Weight: 15%)
  4. MX Records (Weight: 10%)
  5. Reverse DNS / PTR (Weight: 5%)
  6. TLS/STARTTLS (Weight: 10%)
  7. Blacklist Check (Weight: 20%)
  8. Bulk Sender Compliance (Weight: 10%)
  9. Additional Checks (Weight: 5%)
  10. Gather Domain Information
  11. Parallel Delegation
  12. Aggregate Results

What it can do on your machine

Read from SKILL.md and the folder at commit 182270a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash
    • Grep
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python
    • openssl
    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Email Audit loads about 3k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 1,223 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~97
When it runs · the whole SKILL.md, loaded when a task matches
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Bash, Grep, Glob

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AgriciDaniel/claude-email at commit 182270a, republished under its MIT licence (© AgriciDaniel). 1,223 words, ~2,967 tokens.

Download SKILL.mdSave it as .claude/skills/email-audit/SKILL.md (or your agent's skills folder).
name
email-audit
description
Audits email domain deliverability setup (SPF, DKIM, DMARC, MX records, blacklists, TLS) and generates health score (0-100) with prioritized fix list. Checks bulk sender compliance against Google/Yahoo/Microsoft 2024-2026 requirements. Provides DNS records to add/update. Use when user asks to audit, check, or analyze email deliverability, domain health, or inbox placement.
allowed-tools
Read, Bash, Grep, Glob
user-invocable
false

Email Audit Sub-Skill

Purpose

Performs comprehensive email deliverability auditing for a domain. Checks DNS authentication records (SPF, DKIM, DMARC), infrastructure (MX, PTR, TLS), reputation (blacklists), and bulk sender compliance. Generates a health score (0-100) with prioritized fixes.

Input

  • Domain name: e.g., rankenstein.cloud, example.com
  • Optional: Email volume (triggers bulk sender compliance checks if 5,000+ emails/day)

Audit Categories

1. SPF Record (Weight: 10%)

What to check:

  • SPF record exists at TXT <domain>
  • Valid syntax: starts with v=spf1
  • DNS lookup count (max 10, warn at 8+)
  • Enforcement level: -all (pass), ~all (softfail), ?all (neutral), +all (fail)
  • No multiple SPF records (causes validation failure)
  • Includes are efficient and necessary

Commands:

bash
dig txt <domain> +short | grep "v=spf1"
# or
python scripts/check_deliverability.py <domain> --spf

Scoring:

  • Valid + hard fail (-all): 100 points
  • Valid + soft fail (~all): 70 points
  • Valid + neutral/pass all: 40 points
  • Invalid syntax or 10+ lookups: 20 points
  • Missing: 0 points
2. DKIM Record (Weight: 15%)

What to check:

  • At least one valid DKIM record exists
  • Key length: 2048-bit (required minimum per NIST), 1024-bit (legacy, upgrade recommended)
  • Common selectors: google, default, selector1, selector2, k1, mandrill, dkim

Commands:

bash
dig txt google._domainkey.<domain> +short
dig txt default._domainkey.<domain> +short
dig txt selector1._domainkey.<domain> +short
# Check common selectors

Note: DKIM selectors are not discoverable without prior knowledge. Check common ones and ask user if their email provider uses a specific selector.

Scoring:

  • 2048-bit key found: 100 points
  • 1024-bit key found: 70 points
  • Invalid/weak key: 30 points
  • Missing: 0 points
3. DMARC Policy (Weight: 15%)

What to check:

  • DMARC record exists at TXT _dmarc.<domain>
  • Policy level: p=reject (excellent), p=quarantine (good), p=none (monitoring)
  • Aggregate reporting (rua=) tag present
  • Forensic reporting (ruf=) tag present (optional)
  • Alignment mode: aspf= (SPF) and adkim= (DKIM) - relaxed vs strict
  • Percentage (pct=) should be 100 for full enforcement

Commands:

bash
dig txt _dmarc.<domain> +short

Scoring:

  • p=reject + rua + pct=100: 100 points
  • p=quarantine + rua: 80 points
  • p=none + rua: 40 points
  • p=none without reporting: 20 points
  • Missing: 0 points
4. MX Records (Weight: 10%)

What to check:

  • Valid MX records exist
  • MX hosts resolve to IP addresses
  • Priority ordering is logical
  • Mail provider identification (Google Workspace, Microsoft 365, custom)

Commands:

bash
dig mx <domain> +short
dig a <mx-hostname> +short

Scoring:

  • Valid + all hosts resolve + known provider: 100 points
  • Valid + all hosts resolve: 80 points
  • Valid but some hosts don't resolve: 40 points
  • Missing or invalid: 0 points
5. Reverse DNS / PTR (Weight: 5%)

What to check:

  • PTR records exist for MX server IPs
  • PTR records match forward DNS (hostname matches)

Commands:

bash
dig -x <mx-ip> +short

Scoring:

  • All MX IPs have matching PTR: 100 points
  • Partial PTR coverage: 50 points
  • Missing PTR: 0 points
6. TLS/STARTTLS (Weight: 10%)

What to check:

  • STARTTLS support on MX servers (port 25)
  • TLS version (1.2+ recommended)

Commands:

bash
openssl s_client -starttls smtp -connect <mx-hostname>:25 -brief

Note: This may require network access. If not available, note as "Unable to verify".

Scoring:

  • TLS 1.2+ with STARTTLS: 100 points
  • TLS 1.0/1.1 with STARTTLS: 60 points
  • No STARTTLS: 0 points
7. Blacklist Check (Weight: 20%)

What to check:

  • Domain and MX IP addresses against major blacklists:
    • Spamhaus (SBL, XBL, PBL)
    • Barracuda
    • SORBS
    • SpamCop
    • URIBL
    • Invaluement

Commands:

bash
# Use checkdmarc library if available
python -c "import checkdmarc; print(checkdmarc.check_domains(['<domain>']))"

# Or manual checks
dig <ip>.zen.spamhaus.org +short
dig <ip>.b.barracudacentral.org +short

Scoring:

  • Clean on all lists: 100 points
  • Listed on 1 minor list: 50 points
  • Listed on 1 major list (Spamhaus, Barracuda): 30 points
  • Listed on 2+ major lists: 0 points

Critical: Any listing on major blacklists severely impacts deliverability.

8. Bulk Sender Compliance (Weight: 10%)

Applies to: Domains sending 5,000+ emails/day to Gmail, Yahoo, Microsoft recipients.

Requirements (Google/Yahoo/Microsoft 2024-2026 rules):

  1. Both SPF AND DKIM must pass (not just one)
  2. DMARC policy at minimum p=none with alignment
  3. One-click unsubscribe header (RFC 8058: List-Unsubscribe-Post: One-Click)
  4. Spam complaint rate under 0.3% (target under 0.1%)
  5. Valid forward and reverse DNS (PTR records)
  6. Honor unsubscribe within 2 business days
  7. No impersonation of Gmail/Yahoo/Microsoft from headers
  8. TLS connection for message transmission

Scoring:

  • All 8 requirements met: 100 points
  • 6-7 requirements met: 70 points
  • 4-5 requirements met: 50 points
  • Less than 4 met: 0 points
9. Additional Checks (Weight: 5%)

Bonus points for:

  • BIMI record (Brand Indicators for Message Identification) at TXT default._bimi.<domain>
  • MTA-STS policy at https://mta-sts.<domain>/.well-known/mta-sts.txt
  • TLSRPT record at TXT _smtp._tls.<domain> (TLS reporting)
  • Mail-from domain alignment (DKIM/SPF align with From: domain)

Commands:

bash
dig txt default._bimi.<domain> +short
curl https://mta-sts.<domain>/.well-known/mta-sts.txt
dig txt _smtp._tls.<domain> +short

Scoring:

  • Each bonus feature: +25 points (max 100)

Health Score Calculation

Formula:

Total Score = (SPF × 0.10) + (DKIM × 0.15) + (DMARC × 0.15) + (MX × 0.10) +
              (PTR × 0.05) + (TLS × 0.10) + (Blacklists × 0.20) +
              (Bulk Compliance × 0.10) + (Extras × 0.05)

Score Interpretation:

ScoreRatingStatusAction
90-100ExcellentAll critical checks pass, fully compliantMonitor regularly
75-89GoodMinor issues, generally deliverableFix medium priority items
60-74FairIssues that could impact inbox placementFix high priority items within 1 week
40-59PoorSignificant deliverability risksFix critical items immediately
0-39CriticalMajor issues, emails likely going to spamEmergency fixes required

Workflow

Show full SKILL.md (502 more words)Show less
Step 1: Gather Domain Information

Ask user for:

  • Domain name to audit
  • Approximate email volume (to trigger bulk sender checks)
  • Known DKIM selector (if not using common ones)
Step 2: Parallel Delegation

Spawn these agents in parallel for faster auditing:

Agent 1: email-deliverability

Check DNS authentication records for <domain>:
- SPF record validation
- DKIM record discovery (selectors: google, default, selector1, selector2, k1)
- DMARC policy analysis
- MX record validation
- PTR/reverse DNS check

Return JSON with pass/fail status and raw records.

Agent 2: email-compliance

Check bulk sender compliance for <domain>:
- Verify both SPF and DKIM pass
- Check DMARC alignment
- Note TLS support
- Check for List-Unsubscribe headers (if sample email provided)

Return compliance checklist with met/not met status.

Agent 3: email-reputation (if tools available)

Check reputation for <domain>:
- Blacklist status (Spamhaus, Barracuda, SORBS, SpamCop)
- Historical deliverability issues
- Spam complaint rate (if available)

Return list of blacklist hits and reputation score.
Step 3: Aggregate Results

Collect results from all agents and calculate weighted health score.

Step 4: Generate Prioritized Fix List

Categorize issues by priority:

Critical (Fix Immediately):

  • Blacklist listings
  • Missing SPF/DKIM/DMARC
  • Invalid DNS records
  • MX records not resolving

High (Fix Within 1 Week):

  • Weak SPF enforcement (~all instead of -all)
  • 1024-bit DKIM keys (upgrade to 2048-bit)
  • DMARC policy p=none (upgrade to p=quarantine or p=reject)
  • Missing PTR records

Medium (Fix Within 1 Month):

  • Missing aggregate reporting (rua tag)
  • No TLS/STARTTLS support
  • SPF approaching 10 DNS lookup limit
  • Missing bonus features (BIMI, MTA-STS, TLSRPT)
Step 5: Generate DNS Record Recommendations

Provide exact DNS records to add/update with copy-paste ready values.

Output Format

Structure the audit report as:

  1. Header: ## Email Deliverability Audit: [domain] with date, health score, rating
  2. Authentication table: SPF/DKIM/DMARC with status, score, raw records
  3. Infrastructure table: MX/PTR/TLS with status, score, provider detection
  4. Reputation: Blacklist status across Spamhaus, Barracuda, SORBS, SpamCop
  5. Bulk Sender Compliance: 8-requirement checklist (Google/Yahoo/Microsoft rules)
  6. Bonus Features: BIMI, MTA-STS, TLSRPT, Mail-from alignment
  7. Prioritized Fix List: Critical/High/Medium with impact, fix steps, DNS records
  8. DNS Records to Add: Copy-paste ready TXT/MX records
  9. Next Steps: Immediate, this week, this month, monitoring, re-audit

Use score weights from Health Score Calculation section. Use status badges: ✅ PASS, ⚠️ WARN, ❌ FAIL.

Tools

Run python scripts/check_deliverability.py <domain> --json for automated DNS checks.

Manual DNS commands (used in audit categories above):

  • SPF: dig txt <domain> +short
  • DKIM: dig txt <selector>._domainkey.<domain> +short
  • DMARC: dig txt _dmarc.<domain> +short
  • MX: dig mx <domain> +short
  • PTR: dig -x <ip> +short
  • TLS: openssl s_client -starttls smtp -connect <mx-hostname>:25 -brief

Quality Gates

Before delivering audit results:

  1. All critical checks completed (SPF, DKIM, DMARC, MX, Blacklists)
  2. Health score calculated with breakdown by category
  3. Prioritized fix list generated with specific action steps
  4. DNS records provided in copy-paste ready format
  5. Score interpretation explained with next steps

Error Handling

If DNS queries fail:

  • Note as "Unable to verify" in audit report
  • Provide manual check instructions
  • Suggest alternative DNS servers (8.8.8.8, 1.1.1.1)

If DKIM selector unknown:

  • Check common selectors (google, default, selector1, selector2)
  • Ask user for their email provider's DKIM selector
  • Note as "DKIM selector not found - requires manual verification"

If no MX records found:

  • Critical failure - domain cannot receive email
  • Check if domain uses mail forwarding (Cloudflare, etc.)
  • Provide setup instructions for email hosting

References

Load on demand:

  • references/deliverability-rules.md - Scoring thresholds and compliance rules
  • references/mcp-integration.md - Provider-specific setup and DNS configuration
  • references/compliance.md - Compliance rules and regulatory requirements

Success Criteria

Audit is successful when:

  • Health score accurately reflects deliverability state
  • All critical issues identified with clear severity levels
  • User receives actionable DNS records to implement
  • Fix priority aligns with business impact
  • Re-audit timeframe provided based on score

© AgriciDaniel, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/email-audit of AgriciDaniel/claude-email.

Open the folder on GitHubat commit 182270a

Compare with similar skills

Email Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Email Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Email Audit this skillAgriciDaniel/claude-email130—~3kAutomated safety check: NotesMIT
Email Deliverability Auditgrowthenginenowoslawski/coldoutboundskills751—~3.4kAutomated safety check: PassMIT
Himalaya Email CLIPrismer-AI/PrismerCloud1.6k2 repos~2.3kAutomated safety check: PassMIT
Autopilottokencanopy/e2a193—~2.3kAutomated safety check: PassApache-2.0
Smtp Email Senderopenakita/openakita2k—~693Automated safety check: NotesAGPL-3.0
Deliverability Test Publicgrowthenginenowoslawski/coldoutboundskills751—~1kAutomated safety check: PassMIT

Similar skills

  • Email Deliverability Audit

    growthenginenowoslawski/coldoutboundskills

    Diagnostic audit for a running cold email program. An agent skill from growthenginenowoslawski/coldoutboundskills.

    751 GitHub stars~3.4k tokensUpdated 3 days ago
    Backend & APIsAuto-check passed
  • Himalaya Email CLI

    Prismer-AI/PrismerCloud

    Operates a mailbox from the terminal with the external Himalaya CLI over IMAP, SMTP, Notmuch or Sendmail, separate from any built-in email gateway adapter.

    1.6k GitHub starsUsed in 2 repos~2.3k tokens
    Backend & APIsAuto-check passed
  • Autopilot

    tokencanopy/e2a

    Conversationally configure and operate a policy-first, always-on local e2a email agent.

    193 GitHub stars~2.3k tokensUpdated 3 days ago
    Backend & APIsAuto-check passed
  • Smtp Email Sender

    openakita/openakita

    Send emails via SMTP (Gmail, Outlook, etc.). An agent skill from openakita/openakita.

    2k GitHub stars~693 tokensUpdated 15 days ago
    Backend & APIsAuto-check: notes
  • Deliverability Test Public

    growthenginenowoslawski/coldoutboundskills

    Compare reply rates, bounce rates, and positive reply rates broken down by inbox type (SMTP / Gmail / Outlook) for a Smartlead account.

    751 GitHub stars~1k tokensUpdated 3 days ago
    Backend & APIsAuto-check passed
  • E2a Setup

    tokencanopy/e2a

    A skill your agent uses when a user wants to connect or authorize the e2a MCP server, select or create an agent inbox, verify first-run readiness, or set up a custom email domain.

    193 GitHub stars~820 tokensUpdated 3 days ago
    Backend & APIsAuto-check passed

More from AgriciDaniel/claude-email

  • Email Plan

    AgriciDaniel/claude-email

    Generate comprehensive email marketing strategy with 90-day implementation roadmap.

    130 GitHub stars~4.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Email Check

    AgriciDaniel/claude-email

    Intelligent inbox triage that connects to Gmail or Outlook, scores emails by importance (0-100) using sender recognition, urgency keywords, thread depth, time sensitivity, and business relevance…

    130 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check passed
  • Email Review

    AgriciDaniel/claude-email

    Pre-send email quality review and scoring across 5 dimensions (subject line, copy quality, technical/HTML, deliverability, compliance).

    130 GitHub stars~3.3k tokensUpdated 4 mo ago
    Auto-check: notes
  • Email Sequence

    AgriciDaniel/claude-email

    Designs complete email automation sequences with timing, subject lines, copy, and conditional logic.

    130 GitHub stars~2.8k tokensUpdated 4 mo ago
    Auto-check passed
  • Email

    AgriciDaniel/claude-email

    Comprehensive email management and marketing for any business type.

    130 GitHub stars~2k tokensUpdated 4 mo ago
    Auto-check: notes
  • Email Write

    AgriciDaniel/claude-email

    Compose high-converting emails using proven copy frameworks (PAS, AIDA, BAB, FAB, 4Ps).

    130 GitHub stars~2.8k tokensUpdated 4 mo ago
    Auto-check passed

Questions about Email Audit

What does Email Audit do?

Audits email domain deliverability setup (SPF, DKIM, DMARC, MX records, blacklists, TLS) and generates health score (0-100) with prioritized fix list. Email Audit is an agent skill from AgriciDaniel/claude-email. Audits email domain deliverability setup (SPF, DKIM, DMARC, MX records, blacklists, TLS) and generates health score (0-100) with prioritized fix list.

When should I use Email Audit?

Email Audit fits situations like: user asks to audit; analyze email deliverability; inbox placement.

How do I install Email Audit in Claude Code?

Run `npx skills add AgriciDaniel/claude-email --skill email-audit -a claude-code`. Or copy the skill folder (skills/email-audit in AgriciDaniel/claude-email) into .claude/skills/email-audit in your project. Claude Code loads it when a task matches its description.

How do I install Email Audit in Codex?

Run `npx skills add AgriciDaniel/claude-email --skill email-audit -a codex`. Or copy the skill folder (skills/email-audit in AgriciDaniel/claude-email) into .agents/skills/email-audit in your project. Codex loads it when a task matches its description.

Can I use Email Audit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AgriciDaniel/claude-email --skill email-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/email-audit, .gemini/skills/email-audit, .github/skills/email-audit and .opencode/skills/email-audit in your project.

What does Email Audit need to run?

Going by SKILL.md and its folder, Email Audit needs the command-line tools its instructions call (python, openssl and curl). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Bash, Grep, Glob.

Does Email Audit access the network?

SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Email Audit safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Email Audit use?

Email Audit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Email Audit use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Email Audit?

Skills that share tags, products or a category with Email Audit: Email Deliverability Audit (growthenginenowoslawski/coldoutboundskills, 751 stars), Himalaya Email CLI (Prismer-AI/PrismerCloud, 1.6k stars), Autopilot (tokencanopy/e2a, 193 stars) and Smtp Email Sender (openakita/openakita, 2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Email Audit?

AgriciDaniel (a GitHub user) maintains it in AgriciDaniel/claude-email, which has 130 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on May 23, 2026.

Source: AgriciDaniel/claude-email on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.