mcpField
S
suppression-logic

suppression-logic

github.com/gtmagentsMarketing & growth42873 installsUpdated 30w ago
Repository

About suppression-logic

A marketing skill for defining shared rules that pause outreach across marketing, sales, and customer success. It organizes suppression reasons, detection, ownership, duration, and audit practices.

Key features

  1. 01Categorize suppression reasons
  2. 02Define trigger data and queries
  3. 03Assign override and expiration owners
  4. 04Set cooling periods and reviews
  5. 05Record approvals and change history
  6. 06Create matrices and compliance checklists

Use cases

  1. 01Create global do-not-touch rules
  2. 02Investigate why an account is not contacted
  3. 03Coordinate outreach pauses with legal or finance

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill suppression-logic

After installing, type/suppression-logicin Claude Code to confirm it loaded.

Details

From the project README

Suppression Logic Playbook Skill

When to Use

  • Building global do-not-touch rules shared across marketing, sales, and success workflows.
  • Investigating why an account never triggers despite strong intent scores.
  • Coordinating with legal, finance, or product teams on sensitive outreach windows.

Framework

  1. Reason Taxonomy – categorize suppression triggers (legal/compliance, commercial conflicts, lifecycle constraints, technical issues).
  2. Detection Methods – outline data sources and queries that flag each trigger (support tickets, security incidents, open opps, payment status).
  3. Routing & Ownership – assign who can override or expire each suppression (CSM, legal, exec sponsor).
  4. Duration Logic – define cooling periods, review cadences, and auto-expiration rules.
  5. Audit Trail – log change history, approvals, and tie-ins to automation or orchestrator commands.

Templates

  • Suppression matrix (reason, trigger condition, owner, duration, override path).
  • Compliance checklist for regulated industries (financial services, healthcare).
  • Alert + reporting format for surfaced conflicts.

Tips

  • Mirror CRM/MAP suppression lists to prevent channel drift.
  • Create heartbeat alerts when suppression counts spike unexpectedly.
  • Pair with signal-scoring adjustments so suppressed accounts stop draining rep capacity.

Comments

Markdown supported