improve-retention

Diagnose and fix user retention problems using the Fogg Behavior Model framework.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/tayiorbeii/paperclip-factory-kit-hermes --skill improve-retention-tayiorbeii
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: improve-retention
Source: https://github.com/tayiorbeii/paperclip-factory-kit-hermes/tree/main/skills/paperclip/improve-retention
Command: npx skills add https://github.com/tayiorbeii/paperclip-factory-kit-hermes --skill improve-retention-tayiorbeii

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product teams struggle to understand why users drop off after signup, fail to activate, or churn within the first weeks. This Skill provides a systematic behavior design framework (B=MAP) to diagnose retention failures and design fixes grounded in motivation, ability, and prompt analysis. ## Core Features & Use Cases - Retention Diagnostics: Map metrics like low activation, day-1/day-7/day-30 drop-off, and notification fatigue to specific B=MAP failure modes with concrete remediation steps. - Ability Chain Friction Audits: Evaluate six simplicity factors (time, money, physical effort, mental effort, social deviance, non-routine) to find the weakest link blocking key user behaviors. - Tiny Habits Design: Create Starter Steps, anchor moments, and celebration patterns that wire durable user habits without relying on motivation spikes. - Use Case: A SaaS team sees 60% of new users abandon onboarding. Use this Skill to run a friction audit, shrink the first action to a Starter Step, and redesign prompts around real user events. ## Quick Start Analyze why users drop off after their first session in my onboarding flow and recommend fixes using the B=MAP framework.

Frequently Asked Questions about improve-retention

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose why users drop off after onboarding?▼

Map the drop-off timing to a B=MAP failure mode: day-1 drop-off usually means a failed or mistimed prompt, day-7 means the behavior is too hard once motivation fades, and day-30 means no habit formed. Then run an Ability Chain friction audit on the core action.

What is the Fogg Behavior Model B=MAP?▼

B=MAP states that behavior happens when Motivation, Ability, and a Prompt converge at the same moment. Behaviors above the Action Line occur when prompted; below it, no prompt works. The reliable strategy is increasing ability rather than motivation.

How do I reduce onboarding friction for new users?▼

Audit the six Ability Chain factors: time, money, physical effort, mental effort, social deviance, and non-routine. Fix the weakest link, then shrink the first action to a Starter Step such as filling in one field instead of completing a full profile.

When should I use behavior design versus habit loop frameworks?▼

Use B=MAP when diagnosing activation, friction, and prompt timing problems. For habit loops and variable rewards, use a hooked-model approach; for intrinsic motivation, use a self-determination framework. B=MAP is the diagnostic foundation for the others.

Why do push notifications fail to re-engage users?▼

Prompts sent to users below the Action Line—lacking motivation or ability—are perceived as spam. Switch from time-based notifications to event-based prompts tied to real user context, and only prompt when motivation and ability are sufficient.