Churn Risk Analyzer

v1.0.0

Analyze customer data to score churn risk, categorize accounts, and recommend tailored retention actions for proactive customer success management.

0· 710·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The name, README, and SKILL.md all describe churn-risk scoring from usage, tickets, billing, and engagement data; nothing in the skill's files requests unrelated capabilities (cloud creds, system access, or unusual binaries).
Instruction Scope
Runtime instructions ask the agent to request CSVs/CRM exports or manual descriptions and to produce reports and recommendations — this stays within expected scope. Note: it references external AfrexAI context packs and a revenue calculator (promotional links); the instructions do not direct the agent to send data to those endpoints but a user could be encouraged to follow the links.
Install Mechanism
No install spec or code files (instruction-only). This minimizes disk/write/execution risk.
Credentials
The skill declares no environment variables, credentials, or config paths. Its stated inputs (CSV/CRM/manual data) are appropriate for churn analysis and do not require unrelated secrets.
Persistence & Privilege
Does not request always:true and contains no install hooks or permanent modifications; normal autonomous invocation applies but the skill itself does not request elevated persistence.
Assessment
This skill appears coherent for churn scoring and does not request credentials or install code, but consider the following before use: (1) Only provide customer data you are allowed to share — scrub or anonymize PII if unsure. (2) Prefer exporting and reviewing CSVs locally rather than pasting sensitive data into public chat or unfamiliar integrations. (3) The README links to paid AfrexAI resources — those are external and not required for the skill to work; verify the vendor before purchasing. (4) If you plan to connect this skill to a live CRM or analytics system, use least-privilege API keys/accounts and review where processed data is sent. Finally, note the registry metadata is sparse (no homepage, unknown owner); if you need higher assurance, ask the publisher for provenance or a more detailed description before deploying with real customer data.

Like a lobster shell, security has layers — review code before you run it.

churnvk972tszf3k82h2kptgeqr1fazs812egtcustomer-successvk972tszf3k82h2kptgeqr1fazs812egtlatestvk972tszf3k82h2kptgeqr1fazs812egtretentionvk972tszf3k82h2kptgeqr1fazs812egtrevenuevk972tszf3k82h2kptgeqr1fazs812egtsaasvk972tszf3k82h2kptgeqr1fazs812egt

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments