developer-churn
درک، کاهش و جبران ریزش توسعه‌دهندگان
این اسکیل به فهم دلیل ترک توسعه‌دهندگان، نرخ ریزش، کاربران در معرض ریسک، کمپین بازگردانی و جلوگیری از رفتن به رقیب کمک می‌کند.
چه چیزی می‌گیرید
- تحلیل دلیل ترک
- شناسایی کاربران پرریسک
- کمپین بازگردانی
برای چه کاری خوب است
- محصولات API و SaaS
- تیم‌های رشد
برای چه کاری نیست
- محصولات بدون دادهٔ استفاده
دربارهٔ این اسکیل
Developer Churn
Detailed Guide
Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.
When to Use
Use this skill when the user wants to understand, reduce, or recover from developer churn. Trigger phrases include "why developers leave," "churn rate," "win-back campaign," "at-risk users," "developer retention," "preventing churn," or "competitor switching.".
This skill helps you understand why developers leave, identify at-risk users before they churn, and win back those who've already left. No guilt trips or desperate discounts — just honest understanding and genuine value.
Data and action boundaries
Use only authorized, minimized customer data. Keep identifiers out of reports, honor retention and opt-outs, and do not infer a person's intent from a health score. Draft campaigns locally; sending outreach, enrolling users, offering credits or changing billing needs explicit user authority and actual offer terms. Named vendors are examples, not verified current capabilities.
Limitations
- Use this skill only when the task clearly matches its upstream source and local project context.
- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.