Then comes the core in seven steps. Step 1 pins down the target behaviour in the form who does what at what moment, and explicitly rejects vague goals. Step 2 scores each element of MAP from 1 to 10, with an explanation per element of what the bands mean.
For Motivation, 1 to 3 stands for seeing little value, 4 to 6 for doubt, and 7 to 10 for genuinely wanting it. For Ability, 1 to 3 stands for many barriers, 4 to 6 for moderately difficult, and 7 to 10 for practically no barrier. For Prompt, 1 to 3 stands for no trigger or bad timing, 4 to 6 for a trigger that regularly misses, and 7 to 10 for the right signal at the right moment.
Under Ability, the file names Fogg's six elements of simplicity, and these turn the score into something usable rather than a feeling: time, money, physical effort, mental effort, social deviance and routine. If the behaviour costs little time and money but asks someone to deviate from what the group does, that is an ability problem, not a motivation problem. That distinction is exactly where analyses without a model fall apart.
Step 3 plots the behaviour on the action curve and forces a call on the balance: is this high motivation with low ability, like quitting smoking, is it low motivation with high ability, like doing two push-ups, or does it sit balanced above the Action Line. Step 4 treats the lowest provisional score as a candidate bottleneck, names ties, and chooses one justified first test. Making behaviour easier is a practical preference, not a measured comparative guarantee; supporting actions are labelled.
Step 5 designs two to three concrete interventions in total, focused on the first priority with supporting or alternative elements labelled, and the file provides a repertoire list for each element. To raise ability: cut steps or fields, shorten the time, lower the cognitive load with defaults and pre-filling, make the behaviour socially normal, and attach it to an existing routine, which is called habit stacking.
To raise motivation, explicitly named as a last resort: make the short-term benefit visible, use social proof or norms, scarcity or loss framing, and identity framing along the lines of people like me do this. To design a prompt, the file distinguishes three kinds: an action prompt such as a button or an explicit question, a context prompt such as a notification or email at the right moment, and a person prompt where another human reminds you. The Tiny Habits method works mainly with anchor moments: attach new behaviour to something that already happens, with the example after I make coffee, I do two push-ups.
Step 6 shrinks the behaviour down to the smallest version that still counts. Not thirty minutes of meditation but three breaths. Not adding a lead every day but opening the lead tool once. Step 7 adds the celebration, based on the research that habits anchor mainly through positive emotion right after the behaviour. No reward later, no points system, but an immediate internal celebration that Fogg calls shine, or in a product a micro celebration in the interface at the moment of success.
After that, the file fixes the output into nine blocks with set names, from BEHAVIOUR to EXPECTATION, so that every answer looks the same and you can lay two analyses side by side. The file closes with three fully worked examples, a list of five things the skill never does, and three sources. If you want to learn to build a file like this yourself, writing a SKILL.md NL explains the structure step by step.