improve-retention — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited improve-retention (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Framework for designing products that reliably change behavior. Behavior is not about willpower or motivation — it is a design problem with a predictable equation.
The Fogg Behavior Model = B=MAP. Behavior happens when Motivation, Ability, and a Prompt converge at the same moment.
HIGH ┃
┃ ★ Behavior happens
┃ (above the Action Line)
┃
Motivation ┃━━━━━━━━━━━━━━━━━━━━━━━ ← Action Line
┃
┃ ✗ Behavior fails
┃ (below the Action Line)
LOW ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━
HARD EASY
AbilityThe Action Line: When motivation and ability are sufficient, a prompt causes the behavior; below the line, no prompt works. High motivation compensates for low ability and vice versa. The reliable strategy is making behaviors easier (move right), not pumping up motivation (move up).
Goal: 10/10. When reviewing or creating product behavior design, rate it 0-10 based on adherence to the principles below. A 10/10 means full alignment with all guidelines; lower scores indicate gaps to address. Always provide the current score and specific improvements needed to reach 10/10.
Core concept: Motivation is the energy for action, driven by three core motivators, each with two sides: Sensation (pleasure/pain), Anticipation (hope/fear), Belonging (acceptance/rejection). It is powerful but unreliable.
Why it works: Motivation comes in waves — it spikes (New Year's resolutions, product launches) and crashes (day 3, week 2). Products that depend on high motivation fail when the wave recedes; the best designs work at the trough.
Key insights:
Product applications:
| Context | Application | Example |
|---|---|---|
| Onboarding | Don't count on the new-user spike lasting | First actions work even when excitement fades |
| Re-engagement | Assume returning users have low motivation | Show immediate value before asking for effort |
| Messaging | Tap the right motivator | Social fitness → belonging; financial tool → hope |
Copy patterns:
Ethical boundary: Never manufacture false hope or exploit fear — motivation tactics should connect users to genuine outcomes, not anxiety-driven compulsive usage.
See: references/motivation-waves.md for the three motivators, motivation waves, and designing for troughs.
Core concept: Ability is the capacity to do the behavior — a function of the scarcest resource across six factors (the Ability Chain). If any single link is too weak, the behavior breaks.
Why it works: Unlike motivation, ability can be systematically engineered: every removed field, eliminated step, and preset default moves the behavior right on the model, crossing the Action Line even at low motivation. The Ability Chain gives you the diagnostic — find the weakest link and fix it.
Key insights:
Product applications:
| Context | Application | Example |
|---|---|---|
| Signup | Cut cost across all six factors | One-click SSO removes time, mental effort, non-routine |
| Core action | Fix the weakest link | Mental-effort bottleneck → smart defaults and templates |
| Enterprise adoption | Address social deviance | "Your team already uses this" reduces social risk |
Copy patterns:
Ethical boundary: Reduce friction only on genuinely valuable behaviors — never make it too easy to overspend, over-share, or delete important data without confirmation.
See: references/ability-chain.md for the six factors in detail, friction audit templates, and simplification strategies.
Core concept: The prompt says "do it now." Without one, behavior doesn't happen regardless of motivation and ability. Three types: Person Prompts (internal reminders), Context Prompts (environmental cues), Action Prompts (designed triggers from the product).
Why it works: Teams assume motivation + ability is enough — it isn't, not without a well-timed prompt. But prompts only work above the Action Line: a push notification to someone lacking motivation or ability is spam.
Key insights:
Product applications:
| Context | Application | Example |
|---|---|---|
| Notifications | Prompt only above the Action Line | Send digest when there's content to review, not on a schedule |
| Re-engagement | Tie prompts to real events | "Your report is ready" (event-based, not time-based) |
| Feature discovery | Prompt when motivation and ability align | Feature tour appears when user hits the problem it solves |
Copy patterns:
Ethical boundary: Every prompt should pass the test "Would I appreciate receiving this right now?" — never manipulate through anxiety or manufactured urgency.
See: references/prompt-design.md for prompt types, timing strategies, notification design, and anchor moments.
The practical application of B=MAP: make behaviors so small they need almost no motivation, anchor them to existing routines, and celebrate immediately.
After I [ANCHOR MOMENT], I will [TINY BEHAVIOR], then I [CELEBRATION].Every target behavior has a Starter Step — the tiniest meaningful version:
| Target Behavior | Starter Step | Why It Works |
|---|---|---|
| Complete onboarding | Fill in one field | Momentum from completion |
| Use analytics daily | Open the dashboard | Seeing data creates curiosity |
| Collaborate with team | Send one comment | Social reciprocity kicks in |
Once wired, tiny behaviors grow naturally: open dashboard → check a few metrics → customize → automatic morning habit. Never force scaling — let motivation and momentum drive expansion. The tiny version is the foundation, not a failure.
See: references/tiny-habits.md for the full Tiny Habits recipe, celebration techniques, and scaling patterns.
Fogg's systematic process for lasting behavior change:
What outcome does the user want — their aspiration, not the product's goal ("stay on top of my team's progress", not "increase DAU").
List all possible behaviors that could achieve the aspiration. Be exhaustive — don't commit yet.
Assess each for motivation and ease; plot on a 2×2 of impact vs. feasibility (Focus Mapping).
Shrink the best-matched behavior to its Starter Step; design the prompt; add celebration.
Expand once wired. Fix bottlenecks with the Ability Chain; refine prompt timing from data.
Map B=MAP to product metrics:
| Metric | B=MAP Diagnosis | Action |
|---|---|---|
| Low activation | First action below the Action Line | Shrink onboarding to Starter Step; fix weakest Ability Chain link |
| Day-1 drop-off | Prompt failed or mistimed | Redesign first-day prompts; anchor to an existing routine |
| Day-7 drop-off | Motivation wave receded, behavior too hard | Reduce core action difficulty |
| Day-30 drop-off | Habit didn't form, no internal prompt | Create tiny habit recipe; add celebration loops |
| Low feature adoption | Feature below the Action Line for most users | Friction-audit it; prompt only when motivation is present |
| Notification fatigue | Prompts sent below the Action Line | Cut volume; send only with motivation + ability |
| Mistake | Why It Fails | Fix |
|---|---|---|
| Relying on motivation for retention | Motivation always recedes; products needing it fail at the trough | Make behaviors tiny enough to survive motivation dips |
| Ignoring the Ability Chain bottleneck | You optimized time but the barrier is mental effort or social deviance | Audit all six factors; fix the scarcest resource |
| Prompting below the Action Line | Notifications to unmotivated/unable users = spam | Event-based triggers only when motivation + ability suffice |
| Skipping celebration in onboarding | Without positive emotion, repetition doesn't wire habits | Add success states and micro-celebrations after key actions |
| First action too ambitious | "Complete your profile" is a project, not a behavior | Shrink to Starter Step: one field, one action |
| Copying products without diagnosing B=MAP | A high-motivation audience's design fails yours | Diagnose your users' motivation, ability, and prompt context first |
| Question | If No | Action |
|---|---|---|
| Can a new user do the core action in under 60 seconds? | Ability too low | Friction audit; shrink to Starter Step |
| Does the product work when motivation is low? | Design depends on spikes | Redesign core behaviors for minimal motivation |
| Are prompts tied to real events or anchors? | Prompts feel like spam | Switch to event-based or anchor-based prompts |
| Is there immediate feedback after key actions? | No celebration = no habit wiring | Add success states, progress, social feedback |
| Have you found the weakest Ability Chain link? | Optimizing the wrong thing | Rate each of the six factors 1-5 for the core behavior |
| Do users scale naturally from tiny behaviors? | Forcing complexity too early | Starter Steps; let behaviors grow organically |
Based on BJ Fogg's behavior design research:
BJ Fogg, PhD founded the Behavior Design Lab at Stanford University, where he has researched behavior change since 1998. He created the Fogg Behavior Model (B=MAP), coined the term "behavior design", and trained thousands of innovators — including Instagram co-founder Mike Krieger. Tiny Habits distills two decades of that research: lasting change comes from behaviors that are tiny, anchored, and celebrated.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.