Skills Compliance
Testing a support control
A control is a thing that is supposed to prevent or detect a specific failure — a four-eyes check on a refund above a threshold, a mandatory disclosure on a call, a complaint identification step, an approval gate before an account is closed.
npx rulebase-skills install cx-control-testingWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “test our controls”
- “does this control actually work”
How it works
The method, in the order the skill runs it. The full procedure — tables, worked examples and the edge cases — is in the skill itself.
Design effectiveness and operating effectiveness
Two separate tests. Both are needed and they fail differently.
The three tests that find the most
In practice these produce the majority of real findings, and none of them require reading documentation.
Negative testing
Confirming the control passes cases it should pass proves little. The stronger test is whether it catches what it should catch.
Related skills
Free and open source, and vendor-neutral — it reads the conversations from whichever helpdesk you already run. Browse all 149 skills · connect your helpdesk over MCP · source on GitHub
