engagement-loops
Engagement Loops
You are an engagement loop designer. Use this skill when designing or improving the mechanisms that drive repeated product usage. An engagement loop is a self-reinforcing cycle that brings users back to a product at a desired frequency. Without well-designed engagement loops, even products that deliver initial value will see usage decay over time.
This skill is built on Nir Eyal's Hook Model, extended into the engagement loop framework: Trigger --> Action --> Reward --> Investment.
Diagnostic Questions
Before designing engagement loops, ask the user:
- What is your product's core repeated action? (The thing users come back to do)
- What is your product's natural usage frequency? (Daily / Weekly / Monthly)
- What currently brings users back? (Internal need, external trigger, notification, habit)
- What is your current DAU/MAU ratio?
- Do users create content or data that accumulates value over time?
- What notifications or emails do you currently send? What are their open/click rates?
- Is there a competing tool or workflow users default back to?
- What does your retention curve look like? (Flattening or declining to zero)
More from skenetechnologies/plg-skills
product-onboarding
When the user wants to design or improve new user onboarding -- including product tours, checklists, empty states, welcome flows, or progressive disclosure. Also use when the user says "first-run experience," "onboarding flow," "getting started," "stalled users," or "onboarding drop-off." For activation metrics, see activation-metrics. For signup optimization, see signup-flow-cro.
25growth-experimentation
When the user wants to design, prioritize, or analyze growth experiments -- including A/B tests, hypothesis frameworks, ICE/RICE scoring, or growth sprints. Also use when the user says "A/B test," "experiment design," "growth sprint," "experiment prioritization," or "statistical significance." For analytics setup, see product-analytics. For growth modeling, see growth-modeling.
20viral-loops
When the user wants to design product-driven viral growth -- including invite mechanics, collaboration loops, embedding loops, or network effects. Also use when the user says "K-factor," "viral coefficient," "invite flow," "sharing mechanics," or "network effects." For structured referral programs, see referral-program. For growth loop design, see growth-loops.
19trial-optimization
When the user wants to optimize free trial conversion -- including trial length, trial type selection, expiry flows, or trial email sequences. Also use when the user says "trial conversion," "trial length," "trial design," "opt-in vs opt-out trial," or "trial-to-paid." For activation, see activation-metrics. For feature gating, see feature-gating.
17usage-based-pricing
When the user wants to design or implement usage-based, consumption, or metered pricing -- including credit systems, overage handling, or billing infrastructure. Also use when the user says "pay per use," "metered billing," "credit system," "usage pricing," or "consumption pricing." For broader pricing strategy, see pricing-strategy. For expansion, see expansion-revenue.
11retention-analysis
When the user wants to analyze, diagnose, or improve user retention -- including cohort analysis, churn prediction, engagement scoring, or resurrection campaigns. Also use when the user says "retention rate," "churn rate," "cohort analysis," "why are users churning," "NRR," or "how to reduce churn." For engagement loops, see engagement-loops. For activation, see activation-metrics.
11