Skills CX operations
Dashboard review
Dashboards rarely fail because they lack data. They fail because every tile survived every prior review — nobody owns removal, and adding a metric is free.
npx rulebase-skills install cx-dashboard-reviewWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “clean up the dashboard”
- “too many metrics”
- “which KPIs should we keep”
- “nobody looks at this anymore”
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.
The actionability test
Every tile must pass all five checks. Fail one and it is a candidate for removal, redesign, or demotion to an appendix — not a default keep.
Kill criteria
Remove a tile when any of these is true: No action in twelve months, Duplicate story, Vanity activity, Permanent "WIP", Unstable definition, Unowned alert behaviour.
Audit procedure
Work tile by tile. Do not "review the dashboard" as a single vague task.
Owner per tile
An owner is accountable for: Explaining period-over-period movement in one team meeting, Keeping the registry entry current, Declaring when the tile should be retired, Ensuring denominator and suppression rules are visible.
After the audit
Do not add tiles in the same sprint you remove others without running the same actionability test on the new ones.
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
