Skills CX operations
Executive CX reporting
The usual board pack is a screenshot of the dashboard with forty metrics arranged in a grid. Everyone nods. Nobody decides anything, because the pack answers every question except the one executives actually have: is the operation healthy, and where do we intervene?
npx rulebase-skills install cx-executive-reportingWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “board pack”
- “exec summary for support”
- “what should leadership see”
- “too many metrics on the dashboard”
- “three KPIs for the board”
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 three slots
Every executive CX view needs exactly three headline numbers, one from each lane. More than three and nothing gets remembered; fewer and a lane goes unmonitored.
What the pack contains
Structure beats decoration. A workable executive CX section has four parts, in this order: Verdict, Three numbers, Commentary, Appendix pointer.
Commentary that survives the room
Write for someone who will ask "why?" and "compared to what?" in the same breath.
Relationship to the dashboard
The dashboard exists for operators. The pack exists for decision-makers. They should not be the same document.
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
