- Home
- Skills
- Flpbalada
- My Opencode Config
- Fogg Behavior Model
fogg-behavior-model_skill
136
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill flpbalada/my-opencode-config --skill fogg-behavior-model- SKILL.md11.5 KB
Overview
This skill helps designers and product teams apply the Fogg Behavior Model (B = MAP) to design reliable behavior change. It focuses on diagnosing whether Motivation, Ability, or a Prompt is missing and prescribing targeted interventions. Use it to turn vague goals into specific, testable behavior designs with measurable outcomes.
How this skill works
The skill guides you to define a specific target behavior, score Motivation, Ability, and Prompt, and identify the primary bottleneck. It breaks Ability into six concrete factors (time, money, physical effort, mental effort, social deviance, routine) and maps prompt types to solution patterns (spark, facilitator, signal). Finally, it produces prioritized interventions and success metrics to validate change.
When to use it
- Designing onboarding flows and first-run experiences
- Improving conversion or activation rates
- Increasing adoption of a new feature in a product
- Building or supporting user habits
- Diagnosing and reducing user drop-off in a funnel
Best practices
- Start with a precise behavior: who, what, when, and frequency
- Fix Ability first when possible — reduce friction and steps
- Match prompt type to diagnosis: spark for motivation, facilitator for ability, signal for timing
- Measure baseline and set simple success metrics (rate, time, retention)
- Iterate in small experiments: change one element at a time
Example use cases
- Onboarding: convert new signups into activated users with a one-click starter flow and contextual tooltip
- Feature adoption: surface collaboration tools on the dashboard, add social proof, and prompt in relevant tasks
- Habit formation: design a tiny, anchored behavior (2-minute version) with a daily reminder and celebration
- Newsletter signup: move prompt to the article end after value is delivered and test contextual copy
- Conversion lift: reduce checkout steps, pre-fill fields, and trigger a timely email reminder
FAQ
Prioritize Ability first because it is usually fastest to change; then add prompts and boost motivation as needed.
How specific should the target behavior be?
Very specific: define who, exact action, context or timing, and frequency so you can measure and iterate.