Skills Compliance
Auditing disclosures and consent
Some things have to be said, in a particular way, at a particular point, before something else happens: a recording notification, a right-to-cancel notice, a risk warning, a fee disclosure, a data-sharing consent, a notice that the customer is talking to a machine.
npx rulebase-skills install cx-disclosure-auditWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “did we give the required disclosure”
- “are we capturing consent properly”
- “recording notification audit”
- “check our mandatory notices”
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.
Timing is part of the requirement
A disclosure given after the thing it relates to is usually not a disclosure. Check the sequence, not just the presence: Was the cancellation right explained at the point it applied?.
The three ways script-based assurance fails
1. The channel exception. The script covers voice and the same requirement applies to chat, or the disclosure lives in an email template and the conversation happened in messaging. Enumerate every channel the requirement applies to and test each separately. This is the most productive single check.
Detect on required elements, not on a phrase
An exact-string match under-reports, because legitimate variations exist. A loose keyword match over-reports, because a fragment matches.
Consent has extra requirements
Where the audit concerns consent rather than notification, presence is not sufficiency.
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
