Churn Autopsy Skill for Claude
Post-mortem analysis when a client churns. Takes client history, engagement data, support tickets, usage logs, and exit feedback to produce a comprehensive churn autopsy with root cause classification, timeline of decline, and preventive measures.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/OneWave-AI/claude-skills --skill churn-autopsyThe instruction itself
3 sections, as written by the authorChurn Autopsy
Dissect a client departure with forensic rigor and produce churn-autopsy.md: a historical record and retention playbook that turns a loss into organizational learning.
Contents
references/inputs.md-- required and optional data to gather before analysisreferences/analysis-framework.md-- the six-phase forensic methodreferences/root-cause-taxonomy.md-- root cause categories and subcategoriesreferences/output-template.md-- fullchurn-autopsy.mdreport structurereferences/standards.md-- objectivity, rigor, sensitivity, incomplete-data, and operating rules
Workflow
- Collect. Gather all available inputs per
references/inputs.md. Read provided files directly; query connected CRM and analytics MCP tools for account, usage, and support data. Note any gaps. - Organize. Build the full chronological timeline from first touch to cancellation before attempting analysis.
- Analyze. Apply the six phases in
references/analysis-framework.mdsystematically, without skipping: baseline, timeline of decline, root cause classification, missed warning signs, counterfactual analysis, lessons learned. - Classify. Assign one primary root cause and any contributing causes using
references/root-cause-taxonomy.md. - Draft. Write the report in the structure defined in
references/output-template.md. - Challenge. Review every conclusion against
references/standards.md; attempt to disprove each finding before keeping it. - Finalize. Produce
churn-autopsy.mdwith all sections complete in the current working directory or a user-specified location.
Other skills for the same job
different authors, same section of the catalogue
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
How to use it
Take onewave-ai/churn-autopsy from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.