本文へ移動
cccskills
無料GitHub で公開

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.

インストール方法を見る

含まれるファイル(7)

  • SKILL.md5.1 KB
  • references/confidence-and-scoring.md3.7 KB
  • references/data-templates.md1.1 KB
  • references/dimension-rubrics.md14.5 KB
  • references/output-template.md3.8 KB
  • references/save-plays.md6.2 KB
  • references/signals.md4.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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:

DimensionWeight
Engagement Frequency20%
Support Ticket Volume and Sentiment15%
Feature Adoption20%
NPS/CSAT Scores10%
Billing History10%
Stakeholder Continuity10%
Usage Trends15%

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Audit websites for accessibility issues and WCAG compliance. Use when checking accessibility, fixing a11y issues, or ensuring WCAG compliance.

日本語の概要は準備中です。原文の説明を表示しています。

OneWave-AI/claude-skills3402026年10月2日 更新

Deploy a 2-layer parallel agent hierarchy for large, parallelizable work — big refactors, multi-file migrations, codebase-wide audits, bulk generation. A top-tier commander (Fable or Opus) orchestrates the swarms; the user picks a power level (Max Power / Heavy / Balanced / Economy) that sets the Opus/Sonnet/Haiku model mix per layer. Layer 1 is 3-50+ specialist agents, each with its own full context window; Layer 2 is 2+ sub-agents per member. Includes git safety, tiered sizing, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.

日本語の概要は準備中です。原文の説明を表示しています。

OneWave-AI/claude-skills3402026年10月2日 更新

Use to test whether an AI agent, prompt, or skill actually works before or after it ships — build a small eval set, score runs, and catch regressions when the prompt or model changes. Trigger when the user asks whether a prompt is good, wants to compare models or versions, sees inconsistent agent output, or is about to put an agent in front of customers.

日本語の概要は準備中です。原文の説明を表示しています。

OneWave-AI/claude-skills3402026年10月2日 更新

Deploys swarms of sub-agents for massive parallel data processing tasks. Unlike agent-army (which is for code changes), this is for DATA tasks -- processing 1000 documents, analyzing datasets, bulk content generation. Configurable swarm size, task distribution, result aggregation, progress tracking, and error recovery.

日本語の概要は準備中です。原文の説明を表示しています。

OneWave-AI/claude-skills3402026年10月2日 更新

Designs and deploys custom agent teams for specific business workflows. Interactive discovery of business processes, then generates complete team configurations with specialized agent roles, tool access, communication protocols, and handoff rules.

日本語の概要は準備中です。原文の説明を表示しています。

OneWave-AI/claude-skills3402026年10月2日 更新

Agent-to-Agent (A2A) communication protocol. Connect two or more Claude agents that pass messages, share context, delegate tasks, and collaborate. Implements structured handoffs, shared memory, and multi-agent conversations.

日本語の概要は準備中です。原文の説明を表示しています。

OneWave-AI/claude-skills3402026年10月2日 更新

OneWave-AI のスキルをすべて見る

このスキルの問題を報告する