Sub Churn
v1.0.0Monitor subscription commerce for churn risk—blend account activity signals, payment failure (dunning) tracking, and retention flows including compensation o...
⭐ 0· 64·0 current·0 all-time
byRIJOY-AI@rijoyai
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (subscription churn, dunning, downgrade flows) match the SKILL.md, the included reference playbook, and the mandatory deliverables (dunning templates, downgrade table, retention flows). There are no unrelated requirements (no cloud keys, no unrelated binaries).
Instruction Scope
SKILL.md confines behavior to generating playbooks, templates, and asking for platform/context. It references only local reference files (subscription_churn_playbook.md). It does not instruct reading arbitrary system files, contacting external endpoints, or accessing secrets. The mandatory deliverable policy is strict (always include certain templates when answering churn-related prompts) but is coherent with the skill's purpose.
Install Mechanism
Instruction-only skill with no install spec and no bundled code to execute; lowest-risk install posture. All referenced files are local docs and templates.
Credentials
Skill declares no required environment variables, no primary credential, and no config paths. The merge fields it asks to use (e.g. {{first_name}}, {{update_payment_url}}) are standard templating placeholders and do not imply secret access.
Persistence & Privilege
always is false; user-invocable and autonomous invocation are platform defaults. The skill does not request persistent system changes or modify other skills/config. No elevated persistence privileges requested.
Assessment
This skill appears coherent and low-risk, but before installing: (1) confirm you will not paste real customer PII or raw payment data into prompts (use anonymized examples or placeholders); (2) review and approve any compensation/incentive language with finance and legal to avoid policy or regulatory exposure; (3) validate retry cadence and timezone against your billing platform (Stripe, Chargebee, Shopify) before deploying templates; (4) test templates on a small segment and ensure opt-in/consent and regional subscription law compliance (do not treat this as legal advice). If you need the skill to operate on real exports, ensure the agent has access only to sanitized data and consider adding explicit safeguards or manual review steps.Like a lobster shell, security has layers — review code before you run it.
latestvk978adxecv1z6bgf5te182sfb183k915
License
MIT-0
Free to use, modify, and redistribute. No attribution required.