churn-autopsy
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.
git clone --depth 1 https://github.com/OneWave-AI/claude-skills /tmp/churn-autopsy && cp -r /tmp/churn-autopsy/churn-autopsy ~/.claude/skills/churn-autopsySKILL.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.
Audit websites for accessibility issues and WCAG compliance. Use when checking accessibility, fixing a11y issues, or ensuring WCAG compliance.
Deploy a 2-layer parallel agent hierarchy for large, parallelizable work — big refactors, multi-file migrations, codebase-wide audits, bulk generation. Layer 1 is 3-50+ specialist agents, each with its own full context window; Layer 2 is 2+ sub-agents per member. Includes git safety, tiered sizing, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.
Deploys swarms of sub-agents for massive parallel data processing tasks. Unlike agent-army (which is for code changes), this is for DATA tasks -- processing 1000 documents, analyzing datasets, bulk content generation. Configurable swarm size, task distribution, result aggregation, progress tracking, and error recovery.
Designs and deploys custom agent teams for specific business workflows. Interactive discovery of business processes, then generates complete team configurations with specialized agent roles, tool access, communication protocols, and handoff rules.
Agent-to-Agent (A2A) communication protocol. Connect two or more Claude agents that pass messages, share context, delegate tasks, and collaborate. Implements structured handoffs, shared memory, and multi-agent conversations.
Assesses how ready a business is for AI adoption across six dimensions. Evaluates data maturity, tech stack, team skills, process documentation, budget, and culture. Generates a comprehensive ai-readiness-report.md with scores, gap analysis, and recommended starting points. Aligned with OneWave AI's audit methodology.
Generate animated videos and motion graphics from natural language descriptions. Creates a standalone Vite + React project with Framer Motion scenes that auto-play in the browser. Use when the user wants to create animations, motion graphics, video intros, animated presentations, or product demos.
Generate comprehensive API documentation including endpoint descriptions, request/response examples, authentication guides, error codes, and SDKs. Creates OpenAPI/Swagger specs, REST API docs, and developer-friendly reference materials. Use when users need to document APIs, create technical references, or write developer documentation.