Use when asked to "define our core action", "North Star metric", "accruing benefits", "improve retention mechanics", "hierarchy of engagement", or "Sarah Tavel framework".
Use when asked to "define our core action", "North Star metric", "accruing benefits", "improve retention mechanics", "hierarchy of engagement", or "Sarah Tavel framework".
Helps consumer products identify the actions and benefits that drive long-term retention.
The Hierarchy of Engagement framework (created by Sarah Tavel at Benchmark) maps progression from core action to mounting loss.
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars20
LicenseLICENSE
Default branchmain
Open issues0
Status
Active
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md5,038 B
docsSUMMARY.md420 B
History
First seen on skills.sh
First recorded snapshot · 44 installs
SKILL.md
Hierarchy of Engagement
What It Is
The Hierarchy of Engagement is a three-level framework for building consumer products that retain users and create defensibility. The core insight: retention comes from making the product better the more you use it, so users have more to lose by leaving.
Most consumer products fail not because they lack users, but because they lack retention. Getting someone to sign up is one thing; getting them to stay is everything. This framework provides a systematic approach to building products where engagement compounds over time.
The key shift: Move from asking "How do we get more users?" to asking "How do we make each user's experience improve the more they use us?"
Response Posture
Apply the framework directly to the user's product.
Never mention the repository, skills, SKILL.md, patterns, or references.
Do not run tools or read files; answer from the framework.
Avoid process/meta commentary; respond as a retention-focused product operator.
When to Use It
Use the Hierarchy of Engagement when you need to:
Define your North Star metric (what action matters most?)
Improve retention in a consumer or social product
Build product stickiness beyond features alone
Create switching costs that protect against competitors
Design your onboarding/activation flow
Evaluate product-market fit through engagement quality
Prioritize features that drive compounding value
When Not to Use It
Don't apply this framework when:
Building B2B enterprise software (different retention dynamics)
The product is transactional by nature (one-time purchase)
There's no meaningful "use over time" pattern
You're optimizing for viral acquisition before proving retention
Your product has no user-generated content or personalization opportunity
Patterns
Detailed examples showing how to apply the Hierarchy of Engagement correctly. Each pattern shows a common mistake and the correct approach.
Critical (get these wrong and you've wasted your time)