plugins/faos-cro/skills/customer-success-playbook/SKILL.md
<!-- AUTO-GENERATED by export-plugins.py — DO NOT EDIT --> --- name: customer-success-playbook description: Design onboarding sequences, build customer health scores, analyze churn risk, and plan account expansion. Use when creating CS playbooks, building health scoring models, diagnosing at-risk accounts, or designing renewal strategies. tags: [customer-success, churn, onboarding, retention] --- # Customer Success Playbook Comprehensive framework for customer lifecycle management — from onboa
npx skillsauth add frank-luongt/faos-skills-marketplace plugins/faos-cro/skills/customer-success-playbookInstall 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.
Comprehensive framework for customer lifecycle management — from onboarding through expansion and renewal. Build health scores, predict churn, design intervention playbooks, and maximize net revenue retention.
customer-service-ticket-resolution)customer-service-knowledge-base)customer-service-support-metrics)| Stage | Duration | Key Objective | Primary Metric | |-------|----------|--------------|----------------| | Onboarding | Day 0-30 | Achieve first value milestone | Time-to-First-Value (TTFV) | | Adoption | Day 30-90 | Embed into daily workflow | DAU/WAU ratio, feature breadth | | Value Realization | Day 90-180 | Prove ROI to stakeholders | ROI documented, NPS score | | Expansion | Day 180+ | Grow usage and spend | Expansion revenue, seat growth | | Renewal | 90 days before renewal | Secure renewal commitment | Renewal rate, multi-year conversion | | At-Risk | Any time | Prevent churn | Health score recovery, save rate | | Churned | Post-cancellation | Learn and potentially win back | Churn reason analysis, win-back rate |
Composite score from 6 dimensions, weighted by predictive power:
| Dimension | Weight | Inputs | Score (0-10) | Weighted | |-----------|--------|--------|-------------|----------| | Product Usage | 25% | DAU/WAU ratio, session duration, core feature adoption | | | | Feature Adoption | 20% | % of purchased features actively used, depth of integration | | | | Support Health | 15% | Ticket volume trend, CSAT on tickets, escalation frequency | | | | Engagement | 15% | Executive sponsor activity, QBR attendance, community participation | | | | Billing Health | 15% | Payment on time, no disputes, contract value trend | | | | Sentiment | 10% | NPS/CSAT score, qualitative feedback, renewal intent signals | | | | Total | 100% | | | /100 |
Health Bands: | Band | Score | Action | Cadence | |------|-------|--------|---------| | Healthy | 75-100 | Expansion focus | Monthly check-in | | Neutral | 50-74 | Monitor closely | Bi-weekly check-in | | At-Risk | 25-49 | Intervention playbook | Weekly check-in | | Critical | 0-24 | Executive escalation | Daily engagement |
TTFV Targets by Segment: | Segment | TTFV Target | Definition of "First Value" | |---------|-------------|----------------------------| | Self-Serve / SMB | <24 hours | User completes core action | | Mid-Market | <14 days | Team workflow operational | | Enterprise | <30 days | Department-level adoption |
| Signal | Severity | Detection Method | |--------|----------|-----------------| | Login frequency drops >30% WoW | High | Product analytics | | Executive sponsor leaves company | Critical | LinkedIn monitoring, CRM update | | Support ticket volume spikes 3x | High | Support system alerts | | NPS score drops below 6 | Medium | Survey results | | Payment failure / dispute | High | Billing system alerts | | Feature adoption plateaus at <30% | Medium | Usage analytics | | No engagement with CSM for 30+ days | Medium | CRM activity tracking | | Competitor evaluation signals | Critical | Sales intel, community mentions |
Yellow (Score 25-49):
Red (Score 0-24):
| Signal | Motion | Timing | |--------|--------|--------| | Usage hitting >80% of limits | Upsell (higher tier) | When 70% capacity reached | | Team requesting adjacent features | Cross-sell (add-on module) | During QBR or feature request | | New department asking for access | Land & expand (new business unit) | When internal referral surfaces | | Multi-year renewal discussion | Upsell (commitment discount) | 90 days before renewal | | Champion promoted to exec role | Strategic expand | Within 30 days of role change |
## Quarterly Business Review — [Customer] — Q[X] [Year]
### 1. Value Delivered (15 min)
- Key metrics achieved vs. goals
- ROI quantification
- Success stories / wins
### 2. Product Roadmap Alignment (10 min)
- Upcoming features relevant to customer
- Customer feedback incorporated into roadmap
### 3. Usage & Adoption Review (10 min)
- Health score trend
- Adoption metrics by team/department
- Areas for improvement
### 4. Strategic Planning (15 min)
- Customer's upcoming priorities
- How we can support their goals
- Expansion opportunities
### 5. Action Items (10 min)
- Owner + deadline for each item
- Next QBR date
# At-Risk Account Brief — [Customer Name]
**Health Score:** [X]/100 (Band: [Critical/At-Risk])
**ARR:** $[X] | **Contract Renewal:** [Date]
**CSM:** [Name] | **Escalation Owner:** [Name]
## Risk Summary
- **Primary risk factor:** [description]
- **Duration of decline:** [X weeks/months]
- **Churn probability:** [High/Medium] based on [data points]
## Timeline of Decline
| Date | Event | Health Impact |
|------|-------|--------------|
| | | |
## Intervention Plan
| Action | Owner | Deadline | Status |
|--------|-------|----------|--------|
| | | | |
## Save / Loss Outcome
- **Outcome:** [Saved / Churned / Downgraded]
- **Root cause:** [...]
- **Lesson learned:** [...]
revenue-operations (NRR alignment), analytics-tracking (instrumentation for health scoring)development
<!-- AUTO-GENERATED by export-skills.py — DO NOT EDIT --> --- name: databricks-mlflow-evaluation --- # MLflow 3 GenAI Evaluation ## Before Writing Any Code 1. **Read GOTCHAS.md** - 15+ common mistakes that cause failures 2. **Read CRITICAL-interfaces.md** - Exact API signatures and data schemas ## End-to-End Workflows Follow these workflows based on your goal. Each step indicates which reference files to read. ### Workflow 1: First-Time Evaluation Setup For users new to MLflow GenAI evalu
development
<!-- AUTO-GENERATED by export-skills.py — DO NOT EDIT --> --- name: databricks-lakebase-provisioned --- # Lakebase Provisioned Patterns and best practices for using Lakebase Provisioned (Databricks managed PostgreSQL) for OLTP workloads. ## When to Use Use this skill when: - Building applications that need a PostgreSQL database for transactional workloads - Adding persistent state to Databricks Apps - Implementing reverse ETL from Delta Lake to an operational database - Storing chat/agent m
tools
<!-- AUTO-GENERATED by export-skills.py — DO NOT EDIT --> --- name: databricks-jobs --- # Databricks Lakeflow Jobs ## Overview Databricks Jobs orchestrate data workflows with multi-task DAGs, flexible triggers, and comprehensive monitoring. Jobs support diverse task types and can be managed via Python SDK, CLI, or Asset Bundles. ## Reference Files | Use Case | Reference File | | ----------------------
development
<!-- AUTO-GENERATED by export-skills.py — DO NOT EDIT --> --- name: databricks-genie --- # Databricks Genie Create and query Databricks Genie Spaces - natural language interfaces for SQL-based data exploration. ## Overview Genie Spaces allow users to ask natural language questions about structured data in Unity Catalog. The system translates questions into SQL queries, executes them on a SQL warehouse, and presents results conversationally. ## When to Use This Skill Use this skill when: -