fix(plugins): sync all 171 plugin SKILL.md files with fixed skills/ versions
Propagates Anti-Patterns sections, description rewrites, Required Inputs additions, and Quality Checks format fixes from skills/ to matching plugin SKILL.md copies. https://claude.ai/code/session_01MuGKn3a3Gbqoe8uM5Lmuqt
This commit is contained in:
Mohit
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: churn-analysis
|
||||
description: "Analyse customer churn for a product or cohort and produce a structured churn report. Use when asked to analyse churn, understand why customers are leaving, identify churn patterns, calculate churn rate, or build a churn reduction plan. Produces a churn analysis with rate calculations, categorised reasons, early warning signals, and prioritised interventions."
|
||||
description: "Produce a structured churn analysis that separates avoidable from unavoidable churn. Use when investigating why customers are leaving, identifying at-risk segments, calculating net revenue retention, or building a retention intervention plan. Produces a churn report with rate calculations, categorised reasons by avoidability, segment breakdown, timing analysis, early warning signals, and prioritised interventions ranked by estimated impact."
|
||||
---
|
||||
|
||||
# Churn Analysis Skill
|
||||
@@ -169,6 +169,14 @@ Ranked by estimated impact × feasibility.
|
||||
|
||||
---
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not mix avoidable and unavoidable churn in intervention plans — recommending product fixes for customers who churned due to company shutdown wastes resources
|
||||
- [ ] Do not calculate churn rate using end-of-period customer count as the denominator — this understates churn; always divide churned customers by the starting cohort
|
||||
- [ ] Do not rely solely on exit survey data for churn reasons — response rates are typically low and self-selection biases the sample toward customers who are engaged enough to complete a survey
|
||||
- [ ] Do not recommend interventions without linking them to a specific churn reason — interventions disconnected from root causes will not move retention
|
||||
- [ ] Do not report only gross revenue churn — without net revenue retention (NRR), a healthy-looking retention number can hide a shrinking revenue base
|
||||
|
||||
## Quality Checks
|
||||
|
||||
- [ ] Churn rate is correctly calculated (churned ÷ starting cohort, not end-of-period total)
|
||||
|
||||
@@ -174,3 +174,11 @@ Include:
|
||||
- [ ] ARR at risk is quantified
|
||||
- [ ] Communication plan has owners and dates — not "TBD"
|
||||
- [ ] Language is professional and blameless toward individuals
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not assign blame to individuals — focus on system failures and process gaps
|
||||
- [ ] Do not downplay ARR at risk or describe churn risk vaguely without a number
|
||||
- [ ] Do not leave resolution plan ownership as "TBD" or unassigned
|
||||
- [ ] Do not write the brief without a clear ask from the escalation owner
|
||||
- [ ] Do not omit the customer's own stated position — their perspective must be represented fairly
|
||||
|
||||
@@ -139,3 +139,11 @@ Score each dimension 1–5. Weight as shown. Calculate weighted total out of 100
|
||||
- [ ] Actions have owners and deadlines
|
||||
- [ ] Renewal probability is calibrated against pipeline reality
|
||||
- [ ] Trend arrows reflect direction of change vs. last scorecard, not just current state
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not score health dimensions on gut feel — every score needs specific supporting evidence
|
||||
- [ ] Do not give a Green status to accounts with unresolved P1 issues or missed milestones
|
||||
- [ ] Do not list risks vaguely — "low engagement" without specifics is not actionable
|
||||
- [ ] Do not leave recommended actions without named owners and deadlines
|
||||
- [ ] Do not conflate product usage frequency with product value delivery
|
||||
|
||||
@@ -183,6 +183,14 @@ If the success plan falls off track:
|
||||
- [ ] Plan is written to be shared with the customer — no internal-only commentary in this document
|
||||
- [ ] Executive sponsor is identified and has an engagement role
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not define success metrics that the vendor controls — metrics must reflect the customer's business outcomes
|
||||
- [ ] Do not set milestone dates without customer confirmation — unilateral timelines undermine joint ownership
|
||||
- [ ] Do not create a plan the customer hasn't agreed to — it must be mutual, not a CSM's internal plan
|
||||
- [ ] Do not leave ownership fields blank or assigned to "CS team" — every action needs a named owner
|
||||
- [ ] Do not confuse product adoption milestones with customer business outcomes — both are needed but are not the same
|
||||
|
||||
## Example Trigger Phrases
|
||||
|
||||
- "Build a success plan for [Account Name] who just signed"
|
||||
|
||||
@@ -216,3 +216,11 @@ Prompt questions:
|
||||
- [ ] Roadmap preview links each item to a customer goal
|
||||
- [ ] Mutual commitments section has real owners on both sides
|
||||
- [ ] Customer has at least 20 minutes of airtime in the agenda
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not fill the QBR with product activity metrics — lead with business outcomes the customer cares about
|
||||
- [ ] Do not present a roadmap without linking each item to a customer goal — vendor priorities are not a QBR agenda
|
||||
- [ ] Do not run a QBR as a one-sided presentation — it must include structured time for the customer to speak
|
||||
- [ ] Do not close a QBR without documented mutual commitments with named owners on both sides
|
||||
- [ ] Do not skip the "what's not working" slide — suppressing problems erodes trust and misses renewal risks
|
||||
|
||||
@@ -181,6 +181,14 @@ Prepare for the most likely objections:
|
||||
- [ ] Timeline starts at least 90 days before renewal date
|
||||
- [ ] Objection responses are specific to this account, not generic
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not start renewal conversations less than 90 days before the renewal date for accounts over $50K ARR
|
||||
- [ ] Do not build a renewal strategy without first honestly assessing account health — wishful thinking leads to last-minute churn
|
||||
- [ ] Do not treat all renewal objections as negotiating tactics — some objections signal genuine dissatisfaction that requires resolution first
|
||||
- [ ] Do not offer discounts as the first response to price objections — explore value gaps before reducing price
|
||||
- [ ] Do not close the renewal without confirming the expansion opportunity — every renewal is also an expansion conversation
|
||||
|
||||
## Example Trigger Phrases
|
||||
|
||||
- "Build a renewal playbook for [Account Name] renewing in [Month]"
|
||||
|
||||
Reference in New Issue
Block a user