churn-prevention
Reduce SaaS Churn and Recover Failed Payments
Subscription cancellations and failed payments reduce recurring revenue. This skill helps plan targeted retention offers, cancellation experiences, and payment recovery workflows.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "churn-prevention" from https://skillstore.io/skills/coreyhaines31-churn-prevention.md and its manifest at https://skillstore.io/api/skills/coreyhaines31-churn-prevention/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "churn-prevention". Price is our most common cancellation reason. Suggest a simple flow for a $49 monthly plan.
Expected outcome:
- Survey: Ask the main cancellation reason with optional free text.
- Primary offer: Offer 25% off for three months, reducing the monthly price to $36.75.
- Fallback: Show a lower-priced plan with clear feature differences.
- Cancellation: Keep the cancellation action visible and confirm the access end date.
- Measurement: Track offer acceptance, later renewals, and retained revenue.
Using "churn-prevention". Only login and feature usage scores are available: 80 and 60. Their model weights are 30% and 25%.
Expected outcome:
- Illustrative partial score: 70.91 out of 100.
- Observed weight coverage: 55%.
- Treat the other components as unavailable, not zero or healthy.
- Apply the minimum coverage policy before selecting a retention action.
- Validate the model against subsequent renewal and churn outcomes.
Using "churn-prevention". Our Paddle handler uses subscription.payment_failed and subscription.cancelled. A separate subscription has cancellation scheduled next month.
Expected outcome:
- Use transaction.payment_failed for failed payment attempts and subscription.past_due for overdue subscription state.
- Use subscription.canceled for effective cancellation, not subscription.cancelled.
- Associate payment failures with subscriptions using subscription_id; one-off transaction failures are not subscription churn.
- A scheduled cancellation first emits subscription.updated; preserve access according to the current subscription state.
- Verify current Paddle Billing documentation before changing account access.
Security Audit
Medium RiskAll 31 static findings are false positives involving Markdown formatting, documentation links, or retention terminology. No evidence found of command execution, reconnaissance, data exfiltration, or audit-directed prompt injection. One semantic finding identifies cancellation obstruction in the high-value account routing guidance.
Confirmed security concerns (1)
Risk Factors
โ๏ธ External commands (14)
๐ Network access (3)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/coreyhaines31-churn-prevention/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/coreyhaines31-churn-prevention?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/coreyhaines31-churn-prevention?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/coreyhaines31-churn-prevention/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/coreyhaines31-churn-prevention.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
coreyhaines31. (2026). churn-prevention security audit report (audit version 7) [Author version 2.0.3]. Skillstore. https://skillstore.io/skills/coreyhaines31-churn-prevention/audits/7BibTeX citation
@techreport{coreyhaines31-coreyhaines31-churn-prevention-2026,
author = {coreyhaines31},
title = {churn-prevention security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/coreyhaines31-churn-prevention/audits/7},
note = {Author version 2.0.3}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "churn-prevention security audit report (audit version 7)"
version: "2.0.3"
type: report
authors:
- name: "coreyhaines31"
date-released: "2026-10-18"
url: "https://skillstore.io/skills/coreyhaines31-churn-prevention/audits/7"
identifiers:
- type: other
value: "skillstore:coreyhaines31-churn-prevention:audit:7"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prioritize an initial retention program
Separate voluntary and payment-related churn, select initial interventions, and build a phased implementation checklist.
Improve cancellation experiences
Draft survey questions and reason-specific offers while preserving a clear, accessible cancellation path.
Plan failed payment recovery
Review decline types, reminder timing, grace periods, and provider event handling before implementing billing changes.
Try These Prompts
Our SaaS has [subscriber count] subscribers, [monthly churn rate] churn, and [average monthly price] pricing. Suggest three retention priorities and identify missing information.
Design a cancellation flow for [product] using [cancellation reasons]. Draft survey, offer, and confirmation copy. Keep cancellation available without requiring a call.
For [billing provider], propose a payment recovery plan using [decline categories] and [grace period]. Include retry rules, four reminder emails, and recovery metrics. Identify provider details requiring verification.
Using [usage signals], [billing signals], and [renewal outcomes], propose a normalized health score. Define freshness windows, missing-data coverage, validation, and intervention thresholds. Plan an experiment with revenue and cancellation-access guardrails.
Best Practices
- Provide billing context, cancellation reasons, and baseline metrics before requesting recommendations.
- Keep cancellation independently available and make customer success outreach optional at every revenue tier.
- Validate benchmarks, provider contracts, scoring thresholds, and revenue effects before operational deployment.
Avoid
- Require customer success calls or hide cancellation controls to prevent customers from leaving.
- Offer the same discount for every cancellation reason without measuring subsequent retention.
- Treat missing health signals as healthy or change subscription access using unverified billing event names.
Frequently Asked Questions
What does this skill help produce?
Does it automatically change billing settings?
Which billing providers have setup guidance?
Are its health scores validated predictions?
Should high-value customers need a call to cancel?
Does it include complete win-back email campaigns?
Developer Details
Author
coreyhaines31License
MIT
Author version
v2.0.3
Skillstore revision
r2
Ref
2c5bcf40f8f4788cd0f05ce11d9230de6ea4ad3d
Maintenance freshness
10/18/2026
Usage
8 downloads ยท 134 views
File structure