Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Audits sales and process regulations for staleness, conflicts, or drift from actual operational behavior. Translates approved changes into config proposals rather than hardcoded rule updates. Produces a structured change report with risk classification and rollout recommendations.
Treats regulation updates as repeatable, config-driven audits rather than ad hoc code changes, reducing drift between documented policy and live operational behavior.
When to use it
- Checking if presale discount eligibility rules still match current product offerings
- Flagging conflicting routing rules discovered after a GTM strategy change
- Reviewing regional sales restrictions after a compliance update
- Generating config diffs before a new sales campaign launches
- Auditing qualification criteria following a product line deprecation
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Are our presale eligibility and discount rules still consistent with current operations and recent incidents?
- 1Collect current regulation sources and their version dates
- 2Compare each rule against active operational behavior and recent incident logs
- 3Identify stale, conflicting, or non-executable rules with supporting evidence
- 4Translate approved changes into config proposals covering policy_checks, fact_resolution, and routing impacts
- 5Produce a change report with a staleness matrix, proposed config diffs, risk class, and rollout recommendation
Staleness matrix mapping each rule to its status and evidence, proposed config diffs, and backward-compatibility notes for each change