churn-risk-early-warning
Assess churn risk signals from supplied account data and produce early-warning mitigation drafts.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 81
- Forks
- 17
01 前言 Front Matter
- name
- churn-risk-early-warning
- tags
- [ "client-success", "churn", "risk", "read-only" ]
- version
- 0.1.0
- description
- Assess churn risk signals from supplied account data and produce early-warning mitigation drafts.
02 资源文件 3
- 许可证LICENSE1.0 KB
- 参考文档SOURCE.md431 B
- 参考文档TRUST.auto.yaml2.2 KB
03 SKILL.md 正文
Purpose
Assess churn risk signals from supplied account data and produce early-warning mitigation drafts.
Use when
- Account health appears unstable and early intervention planning is needed.
- You must assess risk from provided evidence without inventing engagement data.
Required inputs
- Supplied account data: delivery status, comms notes, KPI trend snapshots [client-provided].
- Contract/expectation context from context/BRAND-CONTEXT.template.md and context/CLIENT-CONTEXT.template.md.
- Known incidents, blockers, and stakeholder feedback.
Safety/authority
- Use only supplied data; do not infer unprovided usage or sentiment metrics.
- No fabricated root-cause claims; mark uncertain hypotheses clearly.
- Output is read-only assessment and draft mitigation plan.
Workflow
- Compile available risk signals by category (performance, delivery, communication, trust).
- Score confidence and severity based on evidence quality.
- Draft near-term mitigation actions and owner suggestions.
- List missing data required before escalation decisions.
Output format
- Risk snapshot
- Signal table (signal | evidence | severity | confidence)
- Mitigation draft plan
- Missing data and escalation triggers
Quality checks
- Every risk statement references supplied evidence.
- Mitigation recommendations include confidence and dependency notes.
Related skills
monthly-client-review, retention-and-upsell-review, qbr-executive-summary-draft
04 同仓库更多 Skills
recipe-performance
Diagnose a specific MetaMask user flow's real-app performance and Sentry critical-user-flow telemetry with deterministic mm-harness recipes. Use for CUF boundaries, cold/warm/background-resume behavior, latency regressions, lifecycle tags, duplicate or blocking network requests, long tasks, layout/paint cost, screen redraws, React rerenders, or browser trace analysis where tests alone cannot prove the real app.
mexc-spot-websocket
MEXC Spot WebSocket workflows for public streams, protobuf handling, depth maintenance, listen keys, and private streams without exposing API keys.
mexc-spot-rest
MEXC Spot REST workflows for public data, signed account requests, orders, wallet/admin actions, and secure signing without exposing API keys.
mexc-futures-websocket
MEXC Futures WebSocket workflows for public streams, private account/order/position streams, ping/pong, subscriptions, and depth maintenance.
0xklen-version-and-refresh-sanctions-lists
暂无简介
verify-tests-cover-changed-lines
Use when a PR adds code that the existing suite may not exercise. Measures patch coverage — the share of newly changed lines hit by tests — before approving.