nps-breakdown
Check whether the product is improving, and what to fix first. Use when users ask for NPS score, promoter/passive/detractor breakdowns, segment-specific NPS, score drivers, linked opportunities, feedback evidence, NPS changes over time, or what to improve next.
Install
With your agent
Install OMGSkills skill "getdeck-io/plugins:skills/nps-breakdown" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/getdeck-io/plugins /tmp/plugins && ln -s /tmp/plugins/skills/nps-breakdown ~/.claude/skills/nps-breakdownFrom README
NPS Breakdown Goal Explain what is driving NPS, not just what the score is — then say what the AI PM should improve first. Intake Ask only for missing NPS scope that materially changes the analysis. Keep intake lightweight: if the user gives enough context to start, proceed and state assumptions briefly. If the request is broad, ask 2-3 targeted questions before querying Deck. Team, audience, or decision the NPS breakdown should support Time period or comparison window Segment, vertical, persona, plan, region, or account cohort Product area, journey stage, or customer topic to investigate in the NPS drivers Whether to include raw responses, score drivers, opportunities, or all of them Whether the user wants an exec summary, product investigation, or detailed evidence table If no time window is provided, default to the latest available NPS period and state that assumption.
More from this repo
competitive-analyst
Used when the user asks about competitors, competitive landscape, rival products, win/loss vs another vendor,...
discovery-partner
Finds the highest-leverage problem to work on using Deck evidence.
feedback-analyst
Investigates a problem in depth before the AI PM acts.