Churn Prevention
v1.0.0When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when...
⭐ 0· 109·0 current·0 all-time
byMario Karras@mariokarras
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description match the SKILL.md content: guidance for cancel flows, save offers, dunning and health-score recommendations. No unrelated dependencies, binaries, or credentials are requested.
Instruction Scope
Instructions are prescriptive and focused on churn prevention. They explicitly ask the agent to read .agents/product-marketing-context.md (or .claude/product-marketing-context.md) if present — this is relevant context for the task but means the agent will access a local file. The rest of the guidance stays within churn-related scope and defers cross-functional tasks (email sequences, paywalls) to other named skills.
Install Mechanism
No install spec or code files to execute; this is instruction-only, so nothing will be downloaded or written by an installer.
Credentials
The skill declares no environment variables, no primary credential, and no config paths beyond the optional product-marketing-context file. Requested access is proportional to the described task.
Persistence & Privilege
always is false, autonomous invocation is allowed (the platform default), and the skill does not request permanent presence or modify other skills. There are no indications it would escalate privileges or persist beyond normal agent behavior.
Assessment
This skill appears coherent and low-risk: it is a text-only playbook for churn prevention and does not request credentials or install anything. The one practical caution is the optional local file it instructs the agent to read (.agents/product-marketing-context.md or .claude/product-marketing-context.md). Before installing or enabling the skill, inspect that file (if present) and remove any sensitive data (customer PII, payment info, API keys, or secrets). If you want stricter safety, run the skill in a workspace/environment that limits agent file access or provide the needed product-marketing context only via a sanitized input. Finally, note the skill references other skills (email-sequence, paywall-upgrade-cro); if you enable integrations with those, review them separately.Like a lobster shell, security has layers — review code before you run it.
latestvk972p3fsq3c6sw1syv697ps5bs836x0e
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
