skills/nps-response-analyser/SKILL.md
Analyses an NPS score and verbatim response to produce a structured interpretation with recommended follow-up by score band. Goes beyond the number to extract actionable insight from the verbatim and match it to the account context. Use when asked to interpret an NPS response, analyse survey results, determine follow-up for a promoter or detractor, make sense of an NPS verbatim, or when an NPS score arrives and the CSM needs to decide what to do about it. Also triggers for questions about NPS follow-up strategy, survey response interpretation, promoter activation, detractor recovery, or what an NPS score means for a specific account.
npx skillsauth add stephenrogan/csm-skills nps-response-analyserInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Takes an NPS score and verbatim response and produces an actionable interpretation matched to the account context. Most companies collect NPS and do nothing useful with individual responses. This skill ensures every response triggers the right follow-up.
Provide:
What it means: The respondent is actively satisfied. They would recommend your product. This is not just a number -- it is permission to activate the relationship.
Interpretation by verbatim quality:
| Verbatim Type | Interpretation | Follow-Up | |-------------|---------------|-----------| | Specific and enthusiastic ("Your automation features have transformed how we work") | Strong advocacy candidate. The verbatim itself is testimonial material | Thank them within 48 hours. Ask what they value most. Assess advocacy readiness (ca-advocacy-tracker). The verbatim may be usable as a testimonial with permission | | Brief and positive ("Good product") | Satisfied but not passionate. Will recommend if asked but will not advocate proactively | Thank them. Ask a follow-up question to deepen: "What specifically makes it work for your team?" | | High score but no verbatim | Satisfaction is real but unexplored. You do not know what drives it | Thank them. Ask what they value most. This is an information gap you need to close | | High score with a caveat ("Love it but wish you had X") | Satisfied with a specific improvement request | Thank them. Address the request: acknowledge, share roadmap status if relevant, log as product feedback |
Timing: Follow up within 48 hours. The goodwill from a promoter score has a half-life. Waiting a week signals you do not care about their feedback.
What not to do: Do not immediately ask for a G2 review or a reference call. Thank them and explore first. The advocacy ask comes later, once you understand what makes them a promoter.
What it means: Satisfied enough not to leave, not satisfied enough to advocate. The most underserved score band -- most companies ignore passives because they are not in crisis. But passives are one bad experience away from becoming detractors and one great experience away from becoming promoters.
Interpretation by verbatim quality:
| Verbatim Type | Interpretation | Follow-Up | |-------------|---------------|-----------| | Specific improvement suggestion ("Good but reporting could be better") | They know exactly what would make them a 9 or 10. This is a roadmap for earning their loyalty | Thank them. Ask: "If we improved [specific thing], would that change your experience materially?" Then act on the answer | | Vague ("It is fine") | Satisfaction without enthusiasm. The product is meeting minimum expectations but not exceeding them | Thank them. Probe: "What would make this a 9 or 10 for you?" The answer reveals the gap between adequate and excellent | | No verbatim | You know nothing except they are mildly satisfied. The most common and least useful response | Follow up in person: "I noticed your NPS response -- thank you. I want to make sure we are meeting your expectations. What could we be doing better?" |
Timing: Follow up within 72 hours. Passives are not urgent but are important.
The opportunity: Passives are the highest-leverage NPS band to influence. Moving a passive to a promoter (by addressing their specific gap) is more achievable than saving a detractor and has a direct impact on your NPS metric.
What it means: The respondent is unhappy. The severity varies dramatically across the band -- a 6 may be mildly disappointed while a 0 may be actively hostile. The verbatim tells you which.
Interpretation by verbatim quality:
| Verbatim Type | Interpretation | Follow-Up | |-------------|---------------|-----------| | Specific, constructive criticism ("Support is too slow and we cannot get issues resolved") | They are frustrated but still communicating. The frustration is about a specific, addressable issue | Acknowledge within 24 hours. Address the specific issue. Do not defend -- fix. This customer may be saveable if you act fast | | Angry or hostile ("This product is terrible and we regret buying it") | Deep dissatisfaction. This may or may not be saveable depending on the root cause | Acknowledge within 24 hours. Do not respond with data or defence -- respond with empathy and a commitment to investigate. Escalate to your manager. This is a churn risk | | Brief and dismissive ("Not great" or just the score with no verbatim) | Disengaged. Not angry enough to explain why, which may be worse than anger -- it suggests they have stopped caring | Follow up in person, not by email. "I saw your survey response and I want to understand what is driving it. Can we talk?" | | Score 0-3 with no verbatim | The lowest scores with no explanation are the most concerning. This person may have already made their decision | Immediate CSM follow-up. This is a risk signal equivalent to a competitive mention. Treat it with the same urgency |
Timing: Within 24 hours. Every hour without acknowledgement compounds the frustration.
Critical rules for detractor follow-up:
A single score is a data point. Multiple scores over time are a trend. The trend is more important than the number:
| Trend | Interpretation | Action | |-------|---------------|--------| | Improving (6 to 8 to 9) | Whatever you are doing is working. The customer is becoming more satisfied | Continue current approach. Ask what drove the improvement -- reinforce it | | Stable promoter (9, 9, 10) | Strong, consistent satisfaction. Reliable advocacy candidate | Maintain the relationship. Activate for advocacy if not already | | Stable passive (7, 7, 8) | Consistently adequate. Not growing into a promoter | Investigate the gap to 9. Something specific is holding them back | | Declining (9 to 7 to 6) | Something is eroding satisfaction. The current score is less important than the direction | Urgent investigation. What changed between the periods? When did the decline start? | | Volatile (6, 9, 5, 8) | Inconsistent experience. The product or service is unpredictable | Investigate what drives the highs and lows. Stabilise the experience before trying to improve the score |
## NPS Analysis: [Account Name]
**Score:** [0-10] | **Band:** [Promoter/Passive/Detractor]
**Respondent:** [Name, Role]
**Verbatim:** "[their response]"
**Date:** [date]
### Interpretation
[2-3 sentences: what this score and verbatim mean in the context of this account]
### Trend
[If prior scores available: trajectory and what it means]
### Recommended Follow-Up
- Action: [specific next step]
- Channel: [call/email/in-person]
- Timing: [within X hours/days]
- Framing: [how to approach the conversation]
### Account Implications
[What this means for the account's health, renewal, or relationship trajectory]
### Flags
[Risk flag if detractor / Advocacy opportunity if promoter / Improvement opportunity if passive]
development
Structures the CSM's week based on their portfolio status, upcoming events, overdue items, and strategic priorities. Produces a time-blocked plan that balances reactive demands with proactive account management. Use when asked to plan a week, structure daily priorities, build a weekly schedule, allocate time across accounts, manage a busy week, or when a CSM feels overwhelmed and needs to determine where to focus. Also triggers for questions about time management, weekly planning, account prioritisation for the week, daily priority setting, or how to balance competing demands across a portfolio.
development
Constructs a compelling value narrative for a customer account by connecting product usage to business outcomes in the customer's language. Produces different versions for different audiences -- the champion, the CFO, the board. Use when asked to build a value story, articulate ROI, create a business case for the customer, prepare value evidence for a renewal or QBR, or when a CSM needs to translate usage metrics into business impact the customer will recognise. Also triggers for questions about value articulation, ROI storytelling, customer business case, value evidence, or how to prove the product is worth the investment.
data-ai
Takes raw usage data -- even a spreadsheet export or pasted metrics -- and identifies patterns, risks, and opportunities. Translates product analytics into account intelligence a CSM can act on. Use when asked to interpret usage data, analyse product metrics, make sense of a usage report, identify trends in customer behaviour, flag usage-based risks, or when a CSM has data but does not know what it means for the account. Also triggers for questions about usage analysis, product analytics interpretation, behavioural pattern detection, usage-based risk identification, or turning raw metrics into actionable insight.
development
Builds a structured 30-60-90 day plan for a CSM taking over a new book of accounts or joining a new team. Prioritises accounts by risk and value, identifies immediate relationship actions, and structures the ramp to full productivity. Use when asked to plan a book transition, create a new CSM onboarding plan, structure a territory takeover, build a 30-60-90 plan for a new role, or when a CSM is inheriting accounts and needs a systematic approach to getting up to speed. Also triggers for questions about account transitions, new book ramp-up, CSM onboarding to a portfolio, territory planning, or how to take over accounts from another CSM.