cx-demand-driver-attribution

SKILLWorkflowcommunity
v0.0.0rulebase-coMITUpdated 1mo agoSource →

Use to attribute contact volume spikes to product releases, campaigns, billing events and operational changes — with a shared calendar, difference-in-differences thinking and explicit limits on causal claims. Trigger for "what caused the volume spike", demand driver attribution, release drove ticket

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 attribute contact volume spikes to product releases, campaigns, billing events and operational changes — with a shared calendar, difference-in-differences thinking and explicit limits on causal claims. Trigger for "what caused the volume spike", demand driver attribution, release drove tickets, campaign contact uplift, billing run volume, event calendar for support, difference in difference

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.