What is the Suppression logic agent skill?

When to Use Building global do-not-touch rules shared across marketing, sales, and success workflows. What sets it apart is how it narrows suppression logic into one specific workflow rather than a broad, generic prompt.

What inputs does Suppression logic need?

Context the agent needs: your goals, audience, constraints, and any source material the skill asks for.

What does Suppression logic output?

A ready-to-use result: the analysis, copy, or recommendations the agent produces.

Suppression logic

Quick answer

01What is it?: When to Use Building global do-not-touch rules shared across marketing, sales, and success workflows. What sets it apart is how it narrows suppression logic into one specific workflow rather than a broad, generic prompt.
02Inputs: Context the agent needs: your goals, audience, constraints, and any source material the skill asks for.
03Output: A ready-to-use result: the analysis, copy, or recommendations the agent produces.

Add this skill

Install-only

Install as a package

Installs this one skill package for your coding agent, including any supporting files that skill ships with — not every skill in the repository. Read the tutorial.

Terminal

$ npx skills add gtmagents/gtm-agents --skill suppression-logic

Skill instructions

The instruction file for this skill. The skill also includes other files you need to install to use it.

SKILL.md

Preview only — coding agent install

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

Reason Taxonomy – categorize suppression triggers (legal/compliance, commercial conflicts, lifecycle constraints, technical issues).
Detection Methods – outline data sources and queries that flag each trigger (support tickets, security incidents, open opps, payment status).
Routing & Ownership – assign who can override or expire each suppression (CSM, legal, exec sponsor).
Duration Logic – define cooling periods, review cadences, and auto-expiration rules.
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.

Common questions

How do I install Suppression logic in Cursor, Claude Code, or Codex?

Run npx skills add gtmagents/gtm-agents --skill suppression-logic in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only Suppression logic, not every skill in the repository.

Where does Suppression logic come from and what license is it under?

Suppression logic comes from the gtmagents/gtm-agents repository on GitHub. That repository has 297 GitHub stars. The skill is published under the Apache-2.0 license.

Prefer plain text? Read the Suppression logic guide as markdown.