agentleFS
Sign inStart free
OneWave-AIOneWave-AI/claude-skills/churn-autopsy/SKILL.md

churn-autopsy

Skill378 starsChanged 52 days agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Draft: Write the report in the structure defined in references/output-template.md.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Churn 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 analysis
  • references/analysis-framework.md -- the six-phase forensic method
  • references/root-cause-taxonomy.md -- root cause categories and subcategories
  • references/output-template.md -- full churn-autopsy.md report structure
  • references/standards.md -- objectivity, rigor, sensitivity, incomplete-data, and operating rules

Workflow

  1. 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.
  2. Organize. Build the full chronological timeline from first touch to cancellation before attempting analysis.
  3. Analyze. Apply the six phases in references/analysis-framework.md systematically, without skipping: baseline, timeline of decline, root cause classification, missed warning signs, counterfactual analysis, lessons learned.
  4. Classify. Assign one primary root cause and any contributing causes using references/root-cause-taxonomy.md.
  5. Draft. Write the report in the structure defined in references/output-template.md.
  6. Challenge. Review every conclusion against references/standards.md; attempt to disprove each finding before keeping it.
  7. Finalize. Produce churn-autopsy.md with all sections complete in the current working directory or a user-specified location.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free