Token导航 LogoToken导航TokenDH.com
待分类只读github未标认证来源可访问许可证需确认审计通过

retention-engagement保留参与度

Agent Skill

retention-engagement 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

766

周安装

31

GitHub Stars

3

下载量

241
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:retention-engagement(保留参与度)
来源仓库:https://github.com/oldwinter/skills
仓库路径:skills/retention-engagement
安装命令:
npx skills add https://github.com/oldwinter/skills --skill retention-engagement
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/oldwinter/skills --skill retention-engagement

简介

用于处理 GitHub 仓库、Issue 和 Pull Request 协作信息。

  • 适合围绕代码变更和仓库状态进行整理与分析。
  • 可结合来源仓库 README 核验具体用法和权限范围。
  • 安装前建议确认是否会触发命令执行或文件读写操作。
  • retention-engagement 属于待分类类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Retention & Engagement

Scope

Covers

  • Diagnosing retention + engagement (cohorts/curves, frequency, segments, drop-offs)
  • Identifying the activation / “aha moment” and reducing time-to-value
  • Designing habit + re-engagement interventions (daily return, reminders, content loops)
  • Creating accruing value and ethical switching costs (“mounting loss”)
  • Turning insights into a prioritized experiment + measurement plan

When to use

  • “Improve retention / reduce churn”
  • “Increase engagement / DAU/WAU”
  • “Define our activation / aha moment”
  • “D1/D7 retention is low—fix onboarding and time-to-value”
  • “Create a retention experiment backlog and a 30/60/90 plan”

When NOT to use

  • You don’t have (or can’t assume) a stable value proposition / ICP (use problem-definition).
  • You’re primarily deciding pricing/packaging/paywalls (this skill can add retention context but won’t replace pricing work).
  • You need acquisition loop design (use designing-growth-loops).
  • You need to synthesize qualitative churn feedback before proposing experiments (use analyzing-user-feedback or interviews).

Inputs

Minimum required

  • Product + target user/ICP and 1–2 key segments
  • Current stage (pre-PMF / early PMF / growth / mature)
  • Best-available baseline metrics (even rough):

- retention (D1/D7/D30 or weekly cohort), churn, engagement (DAU/WAU/MAU), activation rate, time-to-value

  • Onboarding flow summary (steps/screens + where users drop)
  • Constraints: timebox, engineering/design capacity, allowed channels (email/push/in-app), privacy/legal/brand limits

Missing-info strategy

  • Ask up to 5 questions from references/INTAKE.md, then proceed.
  • If metrics are missing, proceed with explicit assumptions and label confidence.
  • Do not request secrets or PII; prefer aggregated metrics and redacted funnels.

Outputs (deliverables)

Produce a Retention & Engagement Improvement Pack (Markdown in-chat; or as files if requested) containing:

  1. Context snapshot (goal, segments, constraints, timebox)
  2. Metric definitions + guardrails (how “retention” and “engagement” are measured)
  3. Retention + engagement diagnosis (cohorts/curves, segments, drop-offs, churn drivers)
  4. Activation / aha moment definition (candidate behaviors + threshold + validation plan)
  5. Lever hypotheses map (onboarding → habit → accruing value → re-engagement)
  6. Experiment backlog (prioritized; experiment cards with success metrics + guardrails)
  7. Measurement + instrumentation plan (events, dashboards, owners if known)
  8. 30/60/90 execution plan
  9. Risks / Open questions / Next steps (always included)

Templates and checklists:

Workflow (7 steps)

1) Intake + goal framing

  • Inputs: User prompt; references/INTAKE.md.
  • Actions: Define the retention problem (segment, time horizon, metric) and the decision this work will drive (what will change). Confirm constraints (timebox, capacity, channels, privacy/brand).
  • Outputs: Context snapshot + metric definitions draft.
  • Checks: Goal is a sentence with a number and a date (e.g., “Improve paid D30 retention from 18%→24% by end of Q2”).

2) Data + instrumentation sanity check

  • Inputs: Current tracking/events (or best guess), funnel steps, dashboards (if any).
  • Actions: List what you can/can’t measure today. Define the minimum event schema needed to learn (activation, engagement, churn). Identify 1–3 highest-impact instrumentation gaps.
  • Outputs: Instrumentation gap list + “minimum viable measurement” plan.
  • Checks: Every key metric in the goal has a data source or an explicit assumption.

3) Diagnose: where retention fails (and why)

  • Inputs: Baseline metrics, cohorts/curves, funnel drop-offs, segments, any churn feedback.
  • Actions: Build a diagnosis across three failure modes:

- Activation failure (users never reach value) - Engagement decay (users get value once, don’t build a habit) - Monetization churn (value exists, but price/packaging/friction drives churn) Segment results (at least 2 segments) and identify the largest “leak.”

  • Outputs: Retention + engagement diagnosis table + primary failure mode(s).
  • Checks: Diagnosis points to one primary lever to test first (onboarding vs habit vs value vs comms).

4) Define the activation / “aha moment” (data-backed)

  • Inputs: Candidate value behaviors + journey; usage events; retention outcome definition.
  • Actions: Propose 3–5 candidate “aha” behaviors, then define an activation threshold (e.g., “uses X feature twice within 7 days” or “invites 2 teammates + uses 2 key features within 14 days”). Document how you’ll validate (correlation with D30/D60 retention; holdout if possible).
  • Outputs: Activation/aha moment spec + validation plan + tracking requirements.
  • Checks: The activation definition is behavioral and measurable (not a survey response or opinion).

5) Generate lever hypotheses (convert insights → rules)

  • Inputs: Diagnosis + activation spec; constraints.
  • Actions: Create a lever map with hypotheses tied to failure modes:

- Onboarding/time-to-value: get users to aha faster and more reliably - Habit/daily return: design cues, routines, rewards; reduce friction to “come back tomorrow” - Accruing value + mounting loss (ethical): personalization, progress/history, saved work, identity/data repository - Re-engagement: lifecycle messaging, winback, content reminders, in-product nudges Convert each hypothesis into a rule + check (see references/SOURCE_SUMMARY.md).

  • Outputs: Lever hypotheses map + candidate interventions.
  • Checks: Every hypothesis ties to (a) a failure mode, and (b) a measurable leading indicator.

6) Design + prioritize experiments (with measurement)

  • Inputs: Hypotheses; measurement plan; capacity.
  • Actions: Turn top hypotheses into experiment cards (1–2 weeks each). Prioritize using a simple score (Impact × Confidence ÷ Effort). Define success metrics and guardrails; note required instrumentation and rollout/rollback.
  • Outputs: Prioritized experiment backlog + experiment cards + metric/guardrail spec.
  • Checks: Top 3 experiments are runnable with current constraints and have unambiguous “win/lose/learn” criteria.

7) Build the 30/60/90 plan + quality gate

  • Inputs: Draft pack; references/CHECKLISTS.md and references/RUBRIC.md.
  • Actions: Sequence work into a 30/60/90 plan (instrumentation, experiments, analysis cadence). Run the checklist and score the rubric. Always include Risks / Open questions / Next steps.
  • Outputs: Final Retention & Engagement Improvement Pack.
  • Checks: Next 2 weeks of work are unblocked; measurement is in place to learn.

Quality gate (required)

Examples

Example 1 (B2C subscription, churn reduction): “Use retention-engagement. Product: meditation app. Segment: paid subscribers. Baseline: D30 paid retention 22%, churn spikes after week 2. Constraint: 4-week sprint, no major redesign. Output: a Retention & Engagement Improvement Pack with an activation/aha definition, a diagnosis, and a prioritized experiment backlog + 30/60/90 plan.”

Example 2 (B2B SaaS, activation + habit): “New users activate but don’t return weekly. Define our aha moment, identify the biggest engagement decay point, and propose 5 experiments (in-product + email) with success metrics and guardrails.”

Boundary example (upstream problem): “Write a brand new value prop and pick an ICP for our product.” Response: that’s upstream strategy/problem definition; use problem-definition (and optionally PMF measurement) before retention optimization.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

32.85%
按下载量换算79

Claude

31.91%
按下载量换算77

Cursor

20.57%
按下载量换算50

Gemini CLI

10.26%
按下载量换算25

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills