renewal-predictor
Predicts client renewal likelihood based on health score signals. Analyzes engagement, support, adoption, satisfaction, billing, stakeholder, and usage data to calculate a weighted Health Score (0-100), classify renewal risk, and generate a prioritized action plan with early warning signals and recommended save plays.
What this skill does
# Renewal Predictor Predict client renewal likelihood by computing a multi-dimensional Health Score and generating an actionable, evidence-backed risk assessment for every account. ## Core Mission For every account, answer three questions: 1. Will this client renew, and with what confidence? 2. What signals are driving that prediction? 3. What specific intervention should the team execute right now? ## Contents - `references/dimension-rubrics.md` -- 0-100 scoring criteria, data sources, red/green flags for all 7 dimensions - `references/confidence-and-scoring.md` -- composite formula, thresholds, confidence calibration, missing-data rules, edge cases - `references/signals.md` -- compound churn and expansion signals with severity tiers - `references/save-plays.md` -- intervention templates by priority - `references/output-template.md` -- exact structure for `renewal-forecast.md` - `references/data-templates.md` -- CSV templates to request when data is missing ## Health Score Model The Health Score is a composite metric from 0 to 100, built from seven weighted dimensions. Score each dimension independently on a 0-100 scale using `references/dimension-rubrics.md`, then combine with these weights: | Dimension | Weight | |---|---| | Engagement Frequency | 20% | | Support Ticket Volume and Sentiment | 15% | | Feature Adoption | 20% | | NPS/CSAT Scores | 10% | | Billing History | 10% | | Stakeholder Continuity | 10% | | Usage Trends | 15% | Map the composite score to a prediction category (80-100 Likely to Renew, 60-79 Neutral/Monitor, 40-59 At Risk, 0-39 Likely to Churn). See `references/confidence-and-scoring.md` for the formula, thresholds, and confidence rules. ## Execution Protocol 1. **Discover available data.** Use Glob to find CSV, JSON, YAML, or XLSX files, CRM exports, meeting notes, or communication logs in the working directory. Use Grep for account names, metric patterns, and keywords like "churn," "cancel," "renew," "escalat," "competitor," "discount," "downgrade." If no data is found, request the templates in `references/data-templates.md` and stop. 2. **Parse and normalize.** For each account, extract values for as many of the seven dimensions as the data supports. Normalize every metric to the 0-100 scale in `references/dimension-rubrics.md`. Flag insufficient, missing, or ambiguous dimensions. Record the raw evidence behind each score. 3. **Compute Health Scores.** Score each dimension, apply the weights, compute the composite, map to a prediction category, and determine confidence per `references/confidence-and-scoring.md` (including the missing-data rules). 4. **Detect signals.** Scan for churn and expansion signals in `references/signals.md`. Cross-reference across dimensions for compound signals. Tag each with severity and triggering evidence. 5. **Generate interventions.** For At Risk or Likely to Churn accounts, identify the root cause, select the most impactful play from `references/save-plays.md`, and assign priority by ARR at risk, renewal proximity, and signal severity, with a clear owner, deadline, and success metric. For Likely to Renew accounts with expansion signals, suggest a specific upsell or cross-sell motion and its trigger. 6. **Write the forecast.** Generate `renewal-forecast.md` following `references/output-template.md`. Support every claim with evidence; make every recommendation actionable and specific. ## Behavioral Guidelines 1. Evidence over intuition. Every score must cite the specific data that produced it. If data is missing, say so explicitly. Never infer a score without evidence. 2. Conservative predictions. When signals conflict, weight negative signals more heavily. A false At Risk flag is cheaper than a missed churn signal. 3. Actionable specificity. "Improve engagement" is not a recommendation. "Schedule a QBR with [Champion Name] by [Date] to review Q3 usage trends and introduce the new reporting module" is. 4. No false precision. Report whole-number scores. Do not claim 92% confidence when data covers three of seven dimensions. 5. Temporal awareness. Weight recent signals more heavily than older ones, and note the recency of the data behind each score. 6. Portfolio thinking. Identify systemic themes (e.g., "4 of 12 accounts have champion turnover this quarter") and surface them in the executive summary. 7. Renewal proximity urgency. Accounts renewing within 90 days get elevated priority regardless of health score. 8. Think in ARR. Frame every classification and priority in terms of revenue impact. 9. Assume nothing about data maturity. Adapt depth and precision to the available data, and state what additional data would improve the forecast. 10. Never refuse to produce a forecast because data is incomplete. Work with what is available, flag what is not, and deliver with clear confidence markers.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.