Skip to content

ericrisco/rsc-harness / skills/email-deliverability

email-deliverability

Verified

Use when mail already sent lands in spam, is rejected, or fails the Gmail/Yahoo bulk-sender checks and the fix is authentication and reputation, not the sending code: SPF/DKIM/DMARC alignment, domain warmup, spam-complaint rate, one-click unsubscribe, BIMI. NOT putting mail on the wire through a provider API (that is `email-connector`).

FileKindSize
SKILL.mdskill md8.9 KB
evals/README.mdmarkdown1.3 KB
evals/cases.yamlconfig4.4 KB
scripts/verify.shexecutablescript3.2 KB

evals/README.md

View on GitHub
# Evals — email-deliverability

`cases.yaml` holds three blocks. `should_trigger` (7 prompts) are situations this
skill must own — the SPF-passes-but-DMARC-fails alignment trap, domain warmup,
the one-click-unsubscribe rule, the BIMI verified-logo request, and a Spanish
phrasing of the spam-folder flagship. `should_not_trigger` (5 prompts) are
near-misses that each route to a
real sibling (`email-connector`, `newsletter`, `cold-outreach`, `gdpr-privacy`,
`data-policy`) so the boundary is checked, not just recall — the sharpest being
the send-path question that belongs to `email-connector`. `capability` (1
scenario) is an 8k/day Gmail-sender remediation with a `must_include` rubric
covering alignment diagnosis, SPF/DKIM fix, the bulk-sender threshold, one-click
unsubscribe, complaint-rate targets, and staged DMARC tightening.

There is no automated runner. To evaluate, paste each `should_trigger` /
`should_not_trigger` prompt into an agent loaded with the catalog and confirm it
selects (or declines) `email-deliverability` and routes to the named sibling.
For `capability`, run the scenario and check the answer against every
`must_include` line — then run `scripts/verify.sh <path-to-dns-or-config>` to
mechanically confirm the DMARC policy and authentication invariants in any DNS
zone / mail config the answer produces.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall