Churn exit survey analyzer
Skill akhilkannur/marketing-agent-blueprints/skills/churn-exit-survey-analyzer
A curated collection of 100+ actionable system prompts and automation blueprints for simple marketing operations. Includes specialized agents for Competitive Intel, SEO, and Lead Generation.
npx -y skills add akhilkannur/marketing-agent-blueprints --skill churn-exit-survey-analyzerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Exit surveys are often ignored. This agent analyzes open-ended 'Why did you cancel?' responses, clusters them into root causes (e.g., 'Pricing', 'Missing Feature X', 'Poor Support'), and prioritizes product fixes.
SKILL.md
1.5 KB, as published. Nobody here has run it
The Churn Survey Analyzer
Core Instructions
You are a highly specialized AI agent focusing on Retention. Your mission is: Exit surveys are often ignored. This agent analyzes open-ended 'Why did you cancel?' responses, clusters them into root causes (e.g., 'Pricing', 'Missing Feature X', 'Poor Support'), and prioritizes product fixes.
Implementation Workflow
Phase 1: Initialization & Seeding
- Check: Does
exit_surveys.csvexist? - If Missing: Create
exit_surveys.csvusing thesampleDataprovided in this blueprint. - If Present: Load the data for processing.
Phase 2: The Loop
Phase 1: Ingestion
- Input: Load
exit_surveys.csv.
Phase 2: Clustering Group responses:
- Category: Pricing ("Too expensive", "Budget cut").
- Category: Product Gap ("Missing Android app", "Too slow").
- Category: Service ("Rude support").
Phase 3: The Fix
Create churn_reduction_plan.md:
- Top Reason: Pricing (45%).
- Action: "Launch a 'Pause Plan' option for $5/mo instead of full cancellation."
Blueprint ID: churn-exit-survey-analyzer Source: Real AI Examples
Gives 0 of the 12 instructions most analytics metrics skills give
Counted across 368 of the 369 authors here whose files we hold, read 2026-08-06
- read product marketing context before asking questionsin 18 of 368, across 12 files
- use lowercase with underscores for event namesin 16 of 368, across 6 files
- track events for decisions not vanity metricsin 15 of 368, across 5 files
- use object-action format for event namesin 15 of 368, across 8 files
- produce a tracking plan documentin 14 of 368, across 4 files
- Call RUBE_SEARCH_TOOLS first to get current schemasin 13 of 368, across 2 files
- establish consistent event naming conventions before implementingin 10 of 368, across 4 files
- Verify dimension and metric compatibility before reportingin 9 of 368, across 2 files
- Encrypt data at rest and in transitin 9 of 368, across 3 files
- use snake_case for event namesin 9 of 368, across 5 files
- monitor technical health during the testin 9 of 368, across 5 files
- use consistent property namesin 8 of 368, across 4 files
Said here and by no other author read
- check for exit_surveys.csv
- group responses into categories
- create churn_reduction_plan.md
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.