Menu

Individual skill

suppression-logic

0upvotes

Use to define guardrails that pause signal-driven plays when accounts are risky, saturated, or in-flight elsewhere.

plugins/intent-signal-orchestration/skills/suppression-logic/SKILL.md

Read pinned source

Source commit 78e0419f4440bcb43bc80127e174ecf5adef1753

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
438
Repository last updated
Apr 3, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.
Back to top