flpbalada/fb-skills

fogg-behavior-model

Diagnose behavior change with B=MAP motivation, ability, and prompt. Use when users do not take a target action, onboarding stalls, conversion drops, feature adoption lags, or prompts fire at the wrong moment; avoid for full habit-loop design better handled by Hooked.

First seen May 4, 2026

Installation

$ npx skills add flpbalada/fb-skills --skill fogg-behavior-model

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from flpbalada/fb-skills · top by installs.

npx skills add flpbalada/fb-skills

Browse all from flpbalada/fb-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 7
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,870 B
  • docs SUMMARY.md 295 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 13 installs

SKILL.md

Fogg Behavior Model

Behavior happens when motivation, ability, and prompt meet at same moment. If behavior fails, one element is missing.

Goal

  • Define target behavior.
  • Find weak element.
  • Design intervention.
  • Measure behavior change.

Elements

  • Motivation: user wants to act.
  • Ability: action is easy enough.
  • Prompt: trigger appears at the right moment.

Ability factors

  • Time.
  • Money.
  • Physical effort.
  • Mental effort.
  • Social risk.
  • Routine fit.

Ability is limited by hardest factor.

Rules

  • Define behavior specifically.
  • Start by improving ability when unsure.
  • Make action smaller before adding persuasion.
  • Prompt only when user can act.
  • Avoid interruptive prompts.
  • Measure actual behavior, not intent.

Flow

  1. Define target behavior: who, what, when, frequency.
  2. Score motivation, ability, prompt from 1-5.
  3. Find bottleneck.
  4. Break down ability factors.
  5. Choose intervention.
  6. Define success metric.

Resources

Output

## Behavior Analysis

Target behavior: [specific action]
User segment: [who]

## Scores
- Motivation: [1-5] - [evidence]
- Ability: [1-5] - [evidence]
- Prompt: [1-5] - [evidence]

## Bottleneck
- [motivation | ability | prompt]

## Intervention
- [specific change]

## Success Metric
- [behavior rate and target]