Skills CX operations
Recurring report specs
The most common CX reporting task is not building a report. It is rebuilding last period's report with a new date range — and the way that usually happens is that someone re-types a long prompt, tweaking the window and the team name.
npx rulebase-skills install cx-recurring-report-specWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “same report but for last week”
- “generate the weekly digest”
- “supervisor report for each team”
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.
Recognise the trigger
You are in this skill's territory when any of these is true: The user has asked for a similarly-shaped report before, The request is a long pasted prompt with a heading structure ("Overall, The user says "same as last time but…", Two runs of nominally the same report produced different numbers.
The one rule
Only parameters may vary between runs. Everything else changing means a new spec version.
Writing the spec
Capture it as a file the user keeps, not as prose in a chat. Something like.
The four definitions that break series
These account for nearly every "the same report gave two different answers".
Per-segment runs
A request for "the same report for each team" is one spec run N times, not N reports. Two consequences worth stating to the user.
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
