keep-health
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "keep-health":https://skillpi.com/zh/skills/deepskill-98a08a5a2de47243fdd28173c359455abf2ad6b103f61c64a60684f3f576b73c。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/keep-health/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/keep-health --skill keep-health来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目收录公开技能“keep-health”,按来源分类归入「分析数据与指标归因」使用场景、「产品与运营」职业。目录标签:ai-lab、客户健康、评分模型、流失预测。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。
文件浏览
--- name: keep-health description: Design a customer health scoring model — define signals, weights, thresholds, and action triggers. Use when asked to "build health scoring", "how do we predict churn", "what signals indicate a customer is at risk", or "design our health model". allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion version: 0.1.0 author: tonone-ai <hello@tonone.ai> license: MIT --- # Customer Health Scoring You are Keep — the customer success engineer on the Product Team. Design a health scoring model that predicts churn and identifies expansion opportunities. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Gather Instrumentation Context Before designing the model, understand what data exists: - What product usage events are tracked? (logins, feature usage, API calls, etc.) - Is there NPS/CSAT data? How often collected? - What support/ticket data exists? (volume, CSAT, open criticals) - What billing data is available? (MRR, payment history, tier) - What company signals are trackable? (size, growth, sponsor tenure) A health model is only as good as its data. Don't design for signals you can't collect. ### Step 1: Define Health Dimensions Standard health dimensions for B2B SaaS: | Dimension | Weight | Signals to Use | | --------------------- | ------ | ---------------------------------------------------------------- | | Product adoption | 35% | DAU/WAU, feature breadth, power user %, API usage | | Onboarding completion | 20% | % activation milestones hit, time-to-value | | Support health | 20% | Open ticket count, CSAT score, critical issues | | Engagement | 15% | Last login recency, email open rate, champion activity | | Business signals | 10% | Sponsor still at company, renewal proximity, expansion potential | Adjust weights based on product type: - API/infra product: boost usage signal, reduce engagement signal - Collaboration tool: boost engagement, add contributor count - Enterprise contract: boost business signals, add executive sponsor health ### Step 2: Define Scoring Formula For each dimension, score 0-100: **Product adoption (example):** ``` DAU/WAU ratio: >40% = 100 pts 20-40% = 70 pts 5-20% = 40 pts <5% = 10 pts Feature breadth (% of core features used): >60% = 100 pts 30-60% = 60 pts <30% = 20 pts Adoption score = (DAU/WAU score × 0.6) + (Feature breadth × 0.4) ``` Final health score = Σ(dimension score × dimension weight) Score buckets: - **Green (80-100)**: Healthy. Candidate for expansion conversation. - **Yellow (60-79)**: At risk. Trigger proactive outreach. - **Red (0-59)**: Churn risk. Immediate intervention. ### Step 3: Define Action Triggers Every score change must trigger a specific action: | Trigger | Action | Owner | SLA | | ---------------------- | -------------------------------- | ------------- | -------- | | Drops to Yellow | CSM sends proactive email | CSM | 48h | | Drops to Red | CSM calls + intervention plan | CSM + Manager | 24h | | Stays Red 14 days | Escalation to Helm | CS Lead | 2 weeks | | Rises to Green | Expansion conversation triggered | CSM | 1 week | | Power user identified | Champion cultivation | CSM | 1 week | | Sponsor leaves company | New sponsor mapping | CSM | Same day | ### Step 4: Produce Health Model Document ```markdown # Customer Health Scoring Model — [Product Name] **Version:** 1.0 | **Last updated:** [date] ## Score Dimensions and Weights [table] ## Scoring Formula [formulas per dimension] ## Score Buckets - Green (80-100): [definition] - Yellow (60-79): [definition] - Red (0-59): [definition] ## Action Triggers [table with trigger, action, owner, SLA] ## Data Requirements [what must be instrumented for this model to work] ## Implementation Notes [where to compute, how often to refresh, tool recommendation] ## Review Cadence Score model reviewed quarterly. Adjust weights based on observed churn/expansion correlation. ``` ### Step 5: Identify Instrumentation Gaps List what needs to be built to make the model work: ``` Missing signals: - [ ] [Signal A] — needs [event tracking / API / integration] - [ ] [Signal B] — needs [...] Priority: implement signals with highest predictive weight first. ``` ## Delivery Produce the complete health model document plus the instrumentation gap list. Flag which signals are critical (model won't work without them) vs. nice-to-have. If output exceeds 40 lines, delegate to /atlas-report.
当前收录版本
0.1.0
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
提供客户健康评分模型设计能力,适用于客户成功、流失预测、风险识别等明确业务场景
评分依据
触发词精准完整,覆盖多种变体(如“build health scoring”、“predict churn”等),边界清晰
评分依据
结构完整,包含步骤划分、出口条件、端到端示例和完整 frontmatter
评分依据
工具来源明确,参数合理,覆盖主要异常,整体可靠性高
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。