AI Skills Marketplace / Sales Engagement

Cross-Tool Suppression & Consent Ledger Sync

The Cross-Tool Suppression & Consent Ledger Sync skill builds one canonical do-not-contact ledger from multiple outbound tools' exported suppression lists, normalizing email and phone identifiers so the same contact is recognized across formatting differences, and outputs a concrete per-tool sync plan for every compliance gap found.

↗ View Source ⬇ Download Full Repo (.zip)
MIT
License
4 functions
Decision branches
most-restrictive-wins precedence + GDPR erasure review flag
Escalation rules
Yes
Multi-tool support
Aug 17, 2026
Last updated
27/27 passing
Tests
README.md View raw ↗

What this is (and isn’t)

A reconciliation engine, not a live integration with any specific tool’s suppression API. You export each tool’s current suppression list, feed the exports in, and get back one canonical ledger plus a concrete list of exactly which contact needs adding to which tool.

Files

FilePurpose
ledger.jsnormalizeIdentifier(), mergeSuppressionRecords(), buildConsentLedger(), computeSyncPlan() — zero dependencies
test.js27-test suite covering identifier normalization, precedence conflict resolution, gap detection, and sync-plan generation
SKILL.mdFull skill definition, loadable in Claude Code/Desktop

The two real guardrails

Identifier normalization (plus-addressing stripped from email, phone numbers normalized to E.164 for unambiguous formats, genuinely ambiguous formats throw rather than guessing) and most-restrictive-wins conflict resolution: the canonical record always keeps the most severe suppression reason across tools (GDPR erasure > complaint/manual DNC > hard bounce/unsubscribe > soft bounce) but the earliest timestamp, since that is when the contact actually first opted out.

FAQ

Is this skill free to use?

Yes. Free to download and run yourself. MV3 charges $175/hr only for implementation help wiring this into your real tools' actual suppression-list export/import APIs.

Does this connect directly to my sales engagement tools?

No. It is a pure function over the suppression data you export and supply. You still need to pull each tool's current suppression list and push the resulting sync plan back in yourself.

What happens when a contact has a GDPR erasure request in one tool but not others?

The canonical record sets requiresErasureReview: true, a routing signal for human or legal follow-up. This is not legal advice, just a flag that a GDPR erasure claim exists somewhere in the merged records.

How does phone number normalization handle international numbers?

Unambiguous 10-digit and 11-digit (with leading 1) US numbers normalize automatically. Already-E.164 numbers starting with + pass through as-is. Genuinely ambiguous formats throw an error rather than guessing at a country code.

Does my suppression data get sent to MV3?

No. All calculations run entirely in your own environment.

JR
Jordan Reeves
ABM & Outbound Pipeline, MV3 Marketing