keep-health
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".
What this skill does
# 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.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.