Client Retention
v1.0.0Design and implement strategies to reduce client churn, increase recurring revenue, and maximize lifetime value through onboarding, value delivery, check-ins...
⭐ 0· 780·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The SKILL.md content is a client-retention playbook (onboarding, monthly reports, churn signals, upsells). There are no required binaries, env vars, config paths, or install steps that contradict the stated purpose.
Instruction Scope
Instructions are entirely textual guidance and templates (e.g., onboarding checklists, monthly report text). The file instructs that outputs go to workspace/artifacts/ (expected for an instruction-only skill). It does not instruct the agent to read unrelated system files or credentials, but it also does not provide guidance on handling client PII/consent or external integrations (SMS, auto-booking) — those operational details and legal/compliance concerns (e.g., TCPA/GDPR, opt-outs) are left to the integrator.
Install Mechanism
No install spec and no code files; this is instruction-only so nothing is downloaded or written to disk by an installer.
Credentials
The skill requests no environment variables, credentials, or config paths. There is no disproportionate credential or system access requested.
Persistence & Privilege
always is false and model invocation is allowed (platform default). The skill does not request persistent presence or modify system/other-skill settings.
Assessment
This appears to be a harmless, coherent playbook for client retention. Before using it in production: 1) Don’t feed or store client PII into the skill or outputs unless you have consent and a secure storage plan. 2) If you automate SMS, appointments, or emails, verify compliance with local laws (TCPA, CAN-SPAM, GDPR) and implement opt-outs. 3) Review and adapt templates for accuracy and tone before sending to clients. 4) When connecting real tools (calendar, SMS gateway, CRM), only supply the minimum credentials required and use per-service tokens/accounts you can revoke. 5) Validate any third-party claims/statistics cited in the document if you plan to present them to clients.Like a lobster shell, security has layers — review code before you run it.
latestvk97dd3n193mc0kza0khywbvzv5811mn5
License
MIT-0
Free to use, modify, and redistribute. No attribution required.