Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →chunkydotdev/suppression-lists
Manage email suppression lists.
Passed 24 of 25 test cases with the skill, and 16 of 25 without it.
and 11 more in the full report
8 fixed16 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are implementing a webhook listener to handle delivery notifications from our email service provider. Please create a technical specification detailing how our backend should map incoming delivery events—such as bounces, complaints, and unsubscribes—into our suppression database. Include a database schema proposal for suppression records and describe the event processing logic for soft versus hard bounces.
| Checked | Without skill | With skill |
|---|---|---|
| Schema includes a scope attribute to distinguish global, tenant, and campaign level suppressions. | Missed | Passed |
| Soft bounce handling specifies suppressing after 3 soft bounces within a 30-day window. | Missed | Passed |
| Soft bounce suppression includes a 90-day expiration duration. | Missed | Passed |
The instructions your model reads when the skill loads.
Manage bounces, complaints, unsubscribes, and do-not-contact records to protect sender reputation and stay legally compliant.
bounce-handling - retry strategies for soft bounces, processing hard bouncesemail-compliance - CAN-SPAM, GDPR, CASL, unsubscribe requirementssender-reputation - how suppressions protect (and repair) your sending reputationwebhook-processing - handling delivery events that trigger suppressionsdomain-authentication - authentication failures that cause delivery issuesA suppression list is a set of email addresses (or domains) that your system will never send to, regardless of whether they appear in a campaign audience or journey. It is the final gate before mail leaves your infrastructure.
Every email platform maintains one, but the important distinction is scope. You need suppressions at multiple levels:
| Scope | What it covers | Example |
|---|---|---|
| Global | Addresses suppressed across all tenants/accounts | Known spam traps, legal requests |
| Account/tenant | Addresses suppressed for a specific sender | A recipient who complained about your emails |
| Campaign | Addresses suppressed for a specific campaign only | Opt-out from a particular newsletter |
Most platforms only give you account-level suppression. That is not enough if you operate multiple brands, send on behalf of customers, or run different mail streams. Build your suppression model with all three scopes from the start.
test cases passed, vs 16 / 25 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.