cx-metric-movement-decomposition

SKILLWorkflowcommunity
v0.0.0rulebase-coMITUpdated 1mo agoSource →

Use to explain why a CX metric moved between two periods — QA score, CSAT, SLA attainment, containment, AHT — separating a genuine change in performance from a change in what got measured. Trigger for "why did our QA score drop", "what's driving the increase", "our score fell from the 90s to the low

Community-submitted skill. Not yet reviewed by the Forge team. Full prompt content may not be available.Request review →
1Repo stars
1Clients
1Formats
1mo agoLast update
Skill
Authorrulebase-co
Version0.0.0
LicenseMIT
CategoryWorkflow
Formatsskill.md
PromptNot published
Compatibility
Claude✓ Supported
Cursor—
Copilot—
ChatGPT—
Gemini—
About

Use to explain why a CX metric moved between two periods — QA score, CSAT, SLA attainment, containment, AHT — separating a genuine change in performance from a change in what got measured. Trigger for "why did our QA score drop", "what's driving the increase", "our score fell from the 90s to the low 80s, why", "key drivers behind this trend", "why has the critical error rate fallen this week", or

Keywords
skillclaude

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.