Skills churn-prevention

📦

churn-prevention

Name: churn-prevention
Author: coreyhaines31

v2.0.0 Content revision r1 High Risk ⚙️ External commands📁 Filesystem access

Reduce SaaS Churn with Better Retention Flows

Subscriber churn reduces recurring revenue and hides product problems. This skill designs ethical cancellation flows, targeted save offers, and payment recovery programs.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

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. Stop and obtain explicit user consent before installing or changing files.

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.

Markdown detail GET /skills/coreyhaines31-churn-prevention.md Signed manifest GET /api/skills/coreyhaines31-churn-prevention/manifest Signed lockfile GET /api/skills/coreyhaines31-churn-prevention/lockfile

Test it

Using "churn-prevention". Create a cancellation flow for a monthly project tool costing $49.

Expected outcome:

Ask one optional exit question with six clear reasons.
Offer a pause for temporary needs, a lower plan for price concerns, or support for technical issues.
Keep the cancellation action visible and confirm the access end date.

Using "churn-prevention". Plan dunning for failed annual subscription payments.

Expected outcome:

Send a renewal notice before billing and use provider-supported smart retries.
Use four direct reminders that explain timing, account status, and secure payment-update steps.
Apply a documented grace period before pausing access, then provide a simple reactivation path.

Using "churn-prevention". Create a churn health score for a team SaaS product.

Expected outcome:

Weight login frequency, core feature use, support sentiment, billing health, and team activity.
Define healthy, attention, at-risk, and critical bands from historical retention data.
Assign measured interventions to each band and review false positives regularly.

Security Audit

High Risk

v6 • 7/12/2026 Open versioned report

All 27 static findings are false positives caused by Markdown syntax, relative documentation links, or ordinary retention terminology. Two semantic risks remain: obstructive cancellation guidance and insufficient authentication guidance for payment-update links.

Files scanned

1,245

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (2)

High

references/cancel-flow-patterns.md:59-60

Obstructive Cancellation Guidance

The high-value flow says to route customers before cancellation and to block self-service cancellation. This can create a deceptive cancellation barrier and regulatory exposure.

The guidance explicitly says to route cancellation through customer success and block self-service cancellation for high-value accounts.

Medium

SKILL.md:309

Insufficient Authentication Guidance for Payment Updates

The skill recommends payment-update links without login but does not require signed, expiring, customer-bound sessions. An unsafe implementation could permit unauthorized billing changes.

The no-login recommendation is explicit, but a secure implementation could use a signed billing portal link.

Risk Factors

⚙️ External commands (13)

SKILL.md:15 SKILL.md:69-71 SKILL.md:71-158 SKILL.md:158-195 SKILL.md:195-231 SKILL.md:231-239 SKILL.md:239-269 SKILL.md:269-271 SKILL.md:271-409 SKILL.md:409-410 SKILL.md:410-411 SKILL.md:411-412 SKILL.md:412

📁 Filesystem access (2)

SKILL.md:363 SKILL.md:384

Audited by: codex View Audit History →

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.

Open versioned report

Copy report link

https://skillstore.io/skills/coreyhaines31-churn-prevention/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/coreyhaines31-churn-prevention/security.svg)](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 6) [Author version 2.0.0]. Skillstore. https://skillstore.io/skills/coreyhaines31-churn-prevention/audits/6

BibTeX citation

@techreport{coreyhaines31-coreyhaines31-churn-prevention-2026,
  author = {coreyhaines31},
  title = {churn-prevention security audit report (audit version 6)},
  institution = {Skillstore},
  year = {2026},
  number = {6},
  url = {https://skillstore.io/skills/coreyhaines31-churn-prevention/audits/6},
  note = {Author version 2.0.0}
}

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 6)"
version: "2.0.0"
type: report
authors:
  - name: "coreyhaines31"
date-released: "2026-07-12"
url: "https://skillstore.io/skills/coreyhaines31-churn-prevention/audits/6"
identifiers:
  - type: other
    value: "skillstore:coreyhaines31-churn-prevention:audit:6"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Design a Fair Cancellation Flow

Create an exit survey, reason-based offers, clear cancellation controls, and confirmation messaging for a subscription product.

Recover Failed Payments

Plan payment retries, dunning messages, grace periods, and reactivation steps for recurring billing.

Build Retention Campaigns

Translate churn signals and cancellation reasons into targeted outreach, tests, and measurement plans.

Try These Prompts

Draft a Cancellation Flow

Design an ethical cancellation flow for [product], serving [customer type] at [price]. Include one survey, relevant offers, clear cancellation, and confirmation copy.

Map Reasons to Save Offers

Map these cancellation reasons to suitable offers: [reasons]. For each reason, provide one primary offer, one fallback, eligibility rules, and success metrics.

Plan Failed Payment Recovery

Create a dunning plan for [billing provider], [billing interval], and [customer type]. Include retry timing, four messages, a grace period, and reactivation steps.

Build a Retention Experiment System

Use [cohort data], [usage signals], [cancel reasons], and [payment failures] to create a health score and intervention matrix. Define thresholds, experiments, guardrails, and metrics.

Best Practices

Keep the cancellation path clear, accessible, and as easy as signup.
Match each intervention to verified customer behavior or a stated cancellation reason.
Measure retained lifetime value, not only immediate offer acceptance.

Avoid

Do not hide cancellation controls or require unwanted sales contact.
Do not apply the same discount to every customer or cancellation reason.
Do not use sensitive behavioral data without a lawful purpose, consent, and access controls.