Skills Compliance
Evidencing that a change actually happened
Somebody needs to show that a support change was made: a policy updated after a complaint theme, a script corrected after a conduct finding, a new step added after an audit. The evidence usually offered is the approval — a ticket, a meeting minute, a sign-off.
npx rulebase-skills install cx-change-evidenceWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “prove we made that change”
- “when did this policy actually change”
- “did the team adopt the new process”
- “we told everyone”
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.
Four dates, and they are not the same day
Establish each separately: Decision date, Effective date, Communication date, Adoption date.
Evidence for each
Effective date — from the artefact's own version history: knowledge article revisions, macro edit timestamps, scorecard version records, deployment logs, config change history. Where an artefact has no version history, say so; the effective date is then unevidenced and that is itself a finding.
Adoption is usually partial, and the partial part is the finding
Expect a curve, not a step. What matters is where it flattens and who is on the wrong side of it.
Distinguish the change from its effect
Two claims people conflate.
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
