retention-strategy
v1.1.1When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer...
⭐ 0· 102·0 current·0 all-time
byKostja Zhang@kostja94
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (retention, churn prevention) match the instructions: assessing churn types, signals, stages, and producing retention tactics and playbooks. No unrelated binaries, credentials, or config paths are requested.
Instruction Scope
The SKILL.md tells the agent to read .claude/project-context.md or .cursor/project-context.md (Sections 4 and 9) if present; this is coherent for tailoring retention advice but does grant the skill access to project-local documentation. It does not instruct reading system-wide files, environment variables, or sending data to external endpoints.
Install Mechanism
No install spec or code files are present. As an instruction-only skill it performs no on-disk installation and therefore has a minimal install surface.
Credentials
The skill requests no environment variables, credentials, or config paths beyond the project-context files noted in SKILL.md. The requested access is proportional to producing tailored retention guidance.
Persistence & Privilege
Flags show no always:true or other elevated persistence. The skill does not request modifying other skills or system-wide settings and remains user-invocable/autonomous-invocation-default without extra privileges.
Assessment
This skill is instruction-only and appears coherent for delivering retention strategies. Before installing, be aware it will read project-local context files (.claude/project-context.md or .cursor/project-context.md) if present — avoid putting sensitive credentials or secrets in those docs. Because there is no install or external credential use, risk is low; still review the SKILL.md yourself and test with non-sensitive project data if you want to confirm the behavior.Like a lobster shell, security has layers — review code before you run it.
latestvk9795t0vaa27agvm9ek5mm789984hs1v
License
MIT-0
Free to use, modify, and redistribute. No attribution required.