Suppression Architect

    1

    Builds the suppression system that stops you from emailing the wrong person twice.

    $19

    30-day refund guarantee

    Secure checkout via Stripe

    0 installsSecurity scanned

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+17 more

    See it in action

    You say

    I need a suppression strategy. Sources are my Shopify customers (domains), a manual CSV of competitors (domains), and my Apollo unsubscribe list (emails). We send via Instantly and Smartlead.

    Your agent does

    Suppression Architecture

    Source Table

    • Shopify Customers: Domain-keyed, Global Scope
    • Competitor CSV: Domain-keyed, Global Scope
    • Apollo Unsubscribes: Email-keyed, Address Scope

    Resolution & Enforcement

    • Key Resolution: Email -> Domain -> Person ID.
    • Enforcement Point: Send-time webhook check.
    • Cross-Campaign Rule: 1 Person : 1 Active Campaign.

    Audit Query SELECT contact_id, check_timestamp FROM outbound_logs WHERE NOT EXISTS (SELECT 1 FROM global_suppression WHERE key = logs.key) AND sent_at > last_sync;

    Re-derive Cadence: Every 24 hours.

    What you get

    Prevent emailing existing customers by mapping domain-level blocks.Synchronize unsubscribes across different outreach platforms and tools.Enforce a one-person-one-campaign rule to stop lead collisions.Generate audit queries to prove compliance during deliverability reviews.

    About this skill

    The problem

    Suppression fails when lists are keyed differently. Email-keyed lists miss domain-level blocks, and import-time suppression goes stale the moment a new lead unsubscribes, leading to compliance risks and angry prospects.

    What it does

    • Maps every suppression source to its natural key (email, domain, or person) without forcing incompatible data types together.
    • Establishes a resolution order to ensure one check consults all identifier types.
    • Architects send-time enforcement to prevent stale data from causing illegal or redundant outreach.
    • Implements cross-campaign rules to ensure one contact is never active in multiple sequences simultaneously.
    • Generates audit queries to prove every sent contact was checked against the full suppression layer.

    Why this beats prompting it yourself

    General prompts often suggest simple list-scrubbing. This skill builds a multi-key resolution system that accounts for the difference between address-level unsubscribes and domain-level customer blocks, ensuring your technical architecture handles edge cases like re-derivation cadence and cross-campaign collisions.

    Use cases

    • Building a global "Do Not Contact" list across multiple outreach tools.
    • Automating customer suppression to prevent emailing existing clients.
    • Managing unsubscribe compliance for high-volume cold email campaigns.
    • Solving lead collisions when running multiple simultaneous sequences.

    Known limitations

    Requires clear definition of your data sources and their primary identifiers to be effective.

    Most premium skills are on a weekly review cycle. Fixes and improvements ship as updates, and buyers receive release notes by email. Part of the Mambabuilt catalog. Packs and the full bundle are available at mambabuilt.com.

    How to install

    Drop the file into your AI Agent. Works with Claude, Cursor, ChatGPT, and 20+ more.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean today

    • One-time purchase, yours forever

    Listedtoday

    Frequently Asked Questions