---
name: email-deliverability-audit
description: "Diagnose email authentication and reputation problems with a prioritized remediation plan. Use when the user requests email deliverability audit. Select relevant methods for the requested outcome; unrelated tasks do not require this skill."
metadata:
  version: "1.0.0"
---

# Email Deliverability Audit

Diagnose email authentication and reputation problems with a prioritized remediation plan.

## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts and required inputs. This generic package contains no client configuration. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for ownership, scheduling and completion. Preserve domain constraints; this Skill creates no competing execution path. Use one method, combine skills, or fill missing steps with authorized tools as the task requires.

External access uses the active Workspace’s approved Outloop capabilities. Never request, read, embed or expose credentials. A service named in a method is a possible dependency, not an access grant. Local file and application work uses the host’s authorized tools.

## Required inputs

- Approved sending domains
- DNS observations
- Message headers
- Delivery and bounce exports

## Methods

### Map authentication

Build a domain-to-provider map from approved inputs. Check SPF mechanisms and lookup limits, DKIM selectors and signatures, and DMARC policy and alignment separately.

### Distinguish delivery states

Distinguish authentication failure, rejected delivery, placement and engagement; an accepted message is not evidence it reached the inbox.

### Compare failure evidence

Compare bounce classes and complaint trends by mailbox and period. Separate reputation concerns from list quality or a broken destination.

### Propose remediation

Propose specific DNS or sending-configuration changes with before/after values and verification steps. Avoid changing DNS, increasing volume or promising deliverability solely from a checklist.

## Completion

Verify findings against source evidence and read back the resulting artifact or authorized change. Report inputs used, methods selected, output location, assumptions and unresolved dependencies. Do not report a plan, queue entry, draft, test fixture or accepted request as a completed external action. Use the task’s requested format; if a tool is unavailable, finish independent work and identify the exact unfulfilled deliverable.

## Test before relying on it

Read [the synthetic evaluation cases](references/evaluation.md) for activation, output and isolation checks. These cases are test instructions, not evidence that a host or provider test has passed.