Use to define guardrails that pause signal-driven plays when accounts are risky, saturated, or in-flight elsewhere.
NewMaintained
Automatic
◆Sales & GTM pack
Last verified 8/23/2026
What it changes
Passed 9 of 22 test cases with the skill, and 13 of 22 without it.
Without skill60%
With skill40%
Checks it passed that the model alone missed
Deploy a compliance checklist tailored for regulated industries
Categorize security incidents under legal or compliance triggers
2 fixed17 passed either way0 still failing3 broke
Pass-rate lift
-20 pp
Tokens
+4%
Agent turns
0%
Response time
-11%
Model gemini-3.6-flashMeasured 8/23/2026v119 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
Our enterprise sales team wants to categorize an active severe security incident investigation at a prospect account under 'lifecycle constraints' to pause outbound SDR calls. How should this risk factor be categorized in a standard B2B suppression taxonomy?
What was checked, without and with the skill
Checked
Without skill
With skill
Categorize security incidents under legal or compliance triggers
Missed
Passed
Reject placing security incident pauses under lifecycle constraints
Passed
Passed
case-01 · gemini-3.6-flash · 8/23/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md25 linessingle file
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.