The AI Hook Model Builder skill for Claude
Describe the product, user and one behaviour you want to support. The skill gathers context, checks ethics before designing a loop, then proposes triggers, an action, reward and investment plus three experiments. Missing current figures remain [TO BE COMPLETED]. Proposed future measurements are not already collected data. The ethics check repeats after synthesis, and the workflow stops when the product does not serve the user.
the lines above come from the zip on this page · SKILL.md is 17,202 bytes
Core behaviour in, complete loop out
reg. H.001This is a shortened conditional teaching example from SKILL.md, not a completed product assessment. The input supplies only a time-tracking app for freelancers, recording today’s hours and daily frequency. Maker use, benefit, working hours, channels and the current form remain unknown. The ethics check happens before design and repeats afterwards; no Facilitator outcome is established here.
What the AI Hook Model Builder is
The AI Hook Model Builder is a free skill from our own library, one of the hundred we give away there with no account and nothing asked in return. A skill is an instruction file, SKILL.md, that gives an AI assistant a fixed method for one task. No software to install, no subscription, no link to your analytics: a single text file of 2,612 words that tells Claude how to fill in the Hook Model, what information it needs for that, in what order it works through the stages and what it may never invent itself. What a skill actually is, and why a plain text file steers an AI's behaviour so strongly, is explained in what are Claude skills NL.
The skill focuses on recurring use rather than pure acquisition or advertising. Users may fail to return for many reasons, including insufficient value, poor fit or unsuitable timing. A loop is one design hypothesis to test, not a universal solution to a forgotten product or a reason to assume that marketing cannot help.
Nir Eyal described a model for this in 2014 in Hooked: four stages that follow each other in a loop, trigger, action, variable reward and investment, as a design hypothesis that useful repeated experiences may encourage return visits. What you get here is not that general explanation, because there is a book for that. It fills the model in for this specific product, this audience and this core behaviour.
It is written for product managers, founders, designers and marketers working on retention, onboarding or activation. You do not need an existing product: with an idea, an audience and a core behaviour you can already work through the stages. What you do need is one action you want to see more often, not a collection. Core behaviour is singular, and that is the first place the skill corrects you.
And then the part that sets this skill apart from most retention advice you find online: the ethics check is a mandatory step, not a footnote. It tests against Eyal's own Manipulation Matrix, and the outcome is explicit. For anything that causes harm with heavy use, such as gambling or impulse credit, it does not build a loop at all. This skill belongs to our AI and automation service and sits alongside the rest of the skill library.
Why users disappear after the first week
The four stages offer questions about cues, actions, rewards and investment. They are an organising model, not a diagnosis that every departing user encountered a broken link. Investigate the product’s actual value, context and possible harms before designing for more frequent use.
The trigger comes at the wrong moment or is not tied to anything. Explore whether the cue fits an existing user need and an appropriate moment. Boredom, unease or fear must not be invented or induced. A proposed connection needs validation; the file no longer predicts that an unsuitable notification is disabled within a week.
The threshold is too high for the motivation that is there. FIG.03 uses Fogg’s conceptual model to investigate motivation, ability and prompt. It does not calculate behaviour or establish that simplifying an action is always cheapest. Seven fields is an added fictional assumption in the example, not proof that ability is the only problem.
The reward does not vary. Distinguish a variable reward from predictable feedback. Predictable feedback can still be useful; reinforcement research does not prove its effect disappears in every product. For each proposed implementation, describe what varies and why that variation serves the task.
The user puts nothing into it. Data, preferences, content, contacts, structure or time may improve usefulness, but those effects and switching costs are hypotheses to test. Identify a possible next cue without trapping the user or assuming that investment always improves the product. An investment that does not load a next trigger does not close the loop, and then you do not have a loop but a straight line with an end.
In diff form: the patterns the skill refuses, next to what it puts in their place. This is not a style preference, it is a hard rule in the file.
Four stages, and then again
reg. H.002The four loop stages below use conditional proposals from the example. The investment may help prepare a useful next cue, but that effect must be tested. The initial ethics gate is required before these stages; the short example does not establish that the product has passed it.
What is really in the SKILL.md
The file has compact frontmatter describing the task, triggers and exclusions. Its full trigger list remains in the opening body, including Hook Model, Nir Eyal, retention, onboarding and recurring-use questions. Pure acquisition, advertising and products harmful through intensive use are excluded. These are instructions to an assistant, not tested guarantees of automatic activation.
After that comes a theory chapter that explicitly names four sources and links each to a stage. Eyal's own Hook Model, the Fogg Behavior Model at the action stage, Skinner at the variable reward, and the IKEA effect plus cognitive dissonance reduction at the investment. The ethics check also comes from Eyal, via the Manipulation Matrix. That is not decoration: because the reasoning sits in the file, Claude can explain, at every choice, why that choice is made rather than just what you have to do.
The core is a fixed method of seven steps, with an initial ethics gate after context and before design, and Step 7 repeated afterwards. Proposals and assumptions must be labelled. Step 1 is the context stage: product, audience, core behaviour and frequency. Core behaviour is one action and not a collection, and frequency is a cadence to assess for this product, not evidence by itself that a habit will form.
After context and the initial ethics assessment, Step 2 proposes external and internal triggers. Step 3 examines motivation, ability and prompt qualitatively, then three feasible simplifications. Step 4 chooses a primary reward type and three implementations with explicit variation. Step 5 tests whether user investment improves usefulness and can support a next cue; increased switching cost is not assumed.
Step 6 summarises the loop in five lines and proposes three two-week experiments. Each needs a hypothesis, comparison, measurement and decision rule, with unwanted effects considered. A noisy result may be inconclusive rather than refuting the hypothesis. Step 7 repeats the ethics assessment already performed before design.
Alongside the seven steps, the file contains an eight-point input checklist, with the instruction to only ask about what is missing, and the rule that a missing figure about current usage is noted as [TO BE COMPLETED] rather than measured itself. The output format has eight parts: context includes the initial ethics outcome, and the final item repeats the check on the proposed design. After that come the shortened example from FIG.01, seven things the skill never does, five honest limits of the framework, and a source list of seven titles.
If you want to write a file like this yourself, or adapt this one to your own product, that is exactly the point: it is released under the MIT licence. Writing a SKILL.md NL explains how to build a file like this, from frontmatter to refusals block.
B = MAP, as a qualitative check
reg. H.003Fogg’s current B = MAP shorthand describes motivation, ability and a prompt converging for a target behaviour. It is not multiplication of measured quantities. The diagram below is a qualitative review of an illustrative scenario. Motivation, the seven-field form and appropriate prompt timing are assumptions to check, not observed scores.
The theory the skill rests on
The SKILL.md closes with seven sources, by name and year, and links each to the stage it belongs to. That is deliberate: it lets you read them yourself and decide whether you agree.
Nir Eyal laid the model down. Hooked, written with Ryan Hoover and published in 2014, describes the four stages and the way they reinforce each other. Eyal also wrote Indistractable in 2019, and that book is not there by accident: it describes the other side, how users arm themselves against loops. Anyone who reads both designs more carefully.
The action stage comes from BJ Fogg. His Behavior Model, presented at the Persuasive conference in 2009, states that behaviour arises when motivation, ability and a prompt come together: the current shorthand B = MAP, a conceptual model rather than multiplication. Fogg also wrote Tiny Habits in 2019, and that is in the list for linking new behaviour to existing routines. That explains why the input checklist explicitly asks whether there is an existing routine the behaviour can latch onto.
Reinforcement research includes Ferster and Skinner. Their 1957 Schedules of Reinforcement examines fixed and variable schedules. That experimental work does not establish that novelty guarantees attention or every predictable product reward stops working. The four-stage product model is not a measured law.
The investment leans on Norton, Mochon and Ariely. Their paper was available online in 2011 and published in the 2012 volume. Successful completion of the studied tasks increased valuation; that does not establish that every product investment increases value or switching cost. That is exactly where the ethical line sits too, because you can use that effect to make something better, or to trap someone.
The context comes from Wood and Neal. Their 2007 paper in Psychological Review describes habit formation as context driven behaviour: the environment sets the action in motion, not a conscious choice. That is why the skill asks for the exact moment and channel for every external trigger. A trigger without context is an idea, not a trigger.
Anyone who wants to apply this way of thinking more broadly than a product can put the Atomic Habits Coach skill alongside it for habits in people rather than in products, or the Fogg Behaviour Model Coach skill for the qualitative model from FIG.03 on its own, apart from the Hook Model. And for the persuasion side of the same question there is the Cialdini Persuasion skill.
Two questions, one honest outcome
reg. H.004The Manipulation Matrix asks whether the maker would use the product and believes it materially improves users’ lives. Two yes answers identify Eyal’s Facilitator quadrant, not measured benefit. This skill additionally asks for evidence or a measurement plan and checks unwanted use before design, then repeats the assessment. Unknown answers stay unknown; a product that does not serve the user is excluded.
# axis 1: would you use the product yourself? · axis 2: do you believe it materially improves users’ lives?
you would use it yourself
you would not use it yourself
for every outcome the file also names the usage pattern you specifically do not want to see and the signal that shows the loop is overshooting · in the example: users who still get nudged late in the evening, and streaks that cause guilt over a holiday
Installing in Claude Code, Claude.ai or Codex
The zip is 6.9 KB and contains one folder, ai-hook-model-builder, with the SKILL.md inside it. Installing is a matter of putting the file in the right place, and that place differs per environment. SKILL.md has been an open standard since December 2025, so the same skill also works in Codex, Cursor and Gemini CLI. So you are not downloading a Claude file but a working instruction any modern AI assistant can read.
- Unzip it into
~/.claude/skills/(or.claude/skills/in your project). - Claude then recognises the skill by itself as soon as you start talking about retention, triggers or habit formation.
- Start Claude Code with claude, then enter
/ai-hook-model-builderinside the session.
- Go to Customize and then Skills.
- Upload the zip there as a skill.
- Or paste the contents of SKILL.md into the project instructions of a Project.
- Open
AGENTS.mdin your repo. - Paste the contents of SKILL.md into it, or put SKILL.md next to it as a separate file and refer to it from
AGENTS.md. - Codex reads that along at every session.
After that, using it is simple: describe your product in one sentence, name your core behaviour and the frequency you want to see, and the skill works through the seven steps. It only asks about what is missing from the eight-point checklist. If you do not have a figure for current usage, that is not a problem: it marks the missing value. Essential benefit or harm information must be clarified before design. If you get stuck on the installation itself, the full route is in installing Claude skills NL. If you want to learn how to set this kind of work up with your team, that is the subject of our AI training.
What the skill refuses
reg. H.005The SKILL.md contains a list of seven things the skill never does, and for a skill about habit formation that list is the most important chapter. You are building behaviour with this. In conversation, those rules play out like this: each rule is a request you might make, with the response the skill gives according to its own instructions.
When you do and do not use it
You get the most out of it with products where repeat use makes the difference: SaaS, apps, services with a digital touchpoint, and anything where the value rises the more often someone uses it. It works just as well for an existing product with a retention problem as for an idea that has not been built yet, because the stages force you into the same choices either way. And it is distinctly useful at onboarding, because that is where the first round through the loop is made.
There are also situations where you are better off leaving it alone, and the file names them itself. For pure acquisition and advertising questions this is the wrong model: that is about the first visit, and the Hook Model is about return visits. And for products that cause harm with heavy use, it refuses to serve.
Then the honest limits of the framework itself, because they are all in there. The model describes behaviour that recurs often, in a short cycle. For products you use twice a year, such as a tax return or a mortgage, it is not the right model. Those infrequent tasks are outside this skill’s intended short-cycle scope.
The evidence is partly practical observation and partly laboratory research. Variable reinforcement is well researched, but the four stages as a whole are an organising model and not a measured law. It is a good way to structure the conversation, not a law of nature you can invoke.
This skill requires a credible user-benefit hypothesis. Habits can also be unhelpful; habit formation does not establish product value. If you doubt whether the underlying usefulness is there, the work starts somewhere else: with testing the assumption itself, for instance with the Mom Test Coach skill for your customer conversations.
Measurements take weeks to months. A two-week experiment gives direction, not proof. And what reads as a friendly reminder in one country or segment feels pushy elsewhere. Test triggers with real users before rolling them out: a plan on paper does not establish that its timing is useful or welcome.
Run it yourself, or have it run for you
reg. H.006This skill is the free do-it-yourself version of work we also deliver as a service. Nothing is held back and there is no catch, but be clear about what a skill is: it teaches your AI how to do something, while every new session starts empty. It is not the engine, and it is not the memory either. You prompt, you supply your product, your core behaviour and your earlier experiments again every time, you check. Anyone who wants it differently has two follow-up steps: hand off the engine, or sort out the memory.
where you are now The skill: you are the engine You run the AI Hook Model Builder yourself in Claude, Codex or Cursor. Costs nothing, works today, and you keep it fully in your own hands: no trial period, no locked-off parts. The limit is your own time: it only happens when you prompt.
having it prepared for you The AI employee: it is ready without you prompting Exactly this work, but as a service: an AI employee prepares recurring work without you having to sit behind Claude for it. Control stays with you, because output stays a draft until a human gives approval. We deliver this through Mansotti, the company TheSEO trades as, which builds the Quote Employee, the Sales Employee and the Reporting Employee. For experiments and loops, the Reporting Employee is the most obvious neighbour, since it delivers the weekly and monthly reports that show whether anything changed. Read what an AI employee is and does.
everything from one source Jarvis: all your AIs work from the same company knowledge The skill teaches the AI, the brain is where the memory lives. Do you want all your AIs to work from the same company knowledge: that is Jarvis, the organisation brain. It connects ChatGPT, Claude, Codex and your people with the same projects, core knowledge and decisions, so your next AI session does not start over. Jarvis selects context, delegates work and keeps only what has been approved: client knowledge stays isolated and every step leaves a checkable trail. This skill benefits from that too, because you no longer have to repeat per session which experiments you already ran and what came out of them. What that delivers in practice, from the plans to your first week, you can read at Jarvis itself.
What Jarvis delivers in practice
reg. H.007Step 3 deserves more than a paragraph, because this is the difference between a smart chat and a system you can build on. Jarvis is the organisation brain: it remembers what your AIs need to know, divides up the work and keeps track of what happened. With experiments that is immediately visible, because an experiment you forget is an experiment you run again.
We have been running on this system ourselves for months. Every agent session, every task and every decision gets logged in it and can be read back. So a new session does not start blank: it first retrieves the logged decisions, the running projects and the latest changes, and carries on from where the previous one stopped. So we are not describing a promise but the way of working we ourselves work in every day.
See the four plans at jarvis/pricing NL. Through the waiting list NL you only pass on your preferred plan, without obligation. That does not create an account, an order or a duty to pay. We discuss business terms separately first.
The skills around it
reg. H.008A hook loop never stands on its own: there is a product underneath it, a measurement alongside it and a choice behind it about what you build first. These skills from the same library each take on a different piece of that chain.
Underneath the loop
the behaviourThe two skills that dig deeper into the behaviour part, each from a different angle.
Fogg Behaviour Model CoachThe qualitative model from FIG.03 on its own, apart from the Hook Model, for when the threshold is your whole problem.SKILL Atomic Habits CoachThe same loop logic, but for habits in people rather than in products.SKILLAlongside the loop
measuring and choosingThe related skills from the growth group. They determine what you measure and what you build first.
AARRR Pirate Metrics CoachPuts retention next to acquisition, activation, referral and revenue, so you know which funnel step is really leaking.SKILL RICE PrioritisationDecides which of the three simplifications you build first, on reach, impact, confidence and effort.SKILL MoSCoW Prioritisation CoachThe faster variant for when you only need to separate what does and does not fit in this sprint.SKILLBefore the loop
the assumptionThis skill requires a credible user-benefit hypothesis before designing a loop. These two help investigate the underlying need.
Mom Test CoachTests your customer interview questions, so you know whether the underlying problem really exists.SKILL Jobs to be Done AnalystSeparates what the user wants to achieve from the feature they happen to suggest.SKILL AIDA CopywriterFor the attention side of the same question: the text that earns the first visit.SKILLLooking further
the contextWhere this skill comes from and what else there is.
The whole skill libraryAll 100 free skills in one place, sorted by topic.HUB AI and automationThe service behind it: from individual skills to working automation in your business.SRV What are Claude skillsThe basics: what a SKILL.md is and why a text file steers an AI's behaviour.DOC NL Knowledge baseArticles on SEO, AI and online visibility, searchable.DOCFrequently asked questions
What does the AI Hook Model Builder skill cost?
Nothing. The skill is free, falls under the MIT licence, and you do not have to create an account or leave an email address. You download a 6.9 KB zip containing a folder and a single file, a 2,612-word SKILL.md, and that is the complete skill. There is no paid version and no sales email follows afterwards.
Does this skill also work in Codex, Cursor or Gemini CLI?
Yes. SKILL.md has been an open standard since December 2025, so the same file also works in Codex, Cursor, Gemini CLI and other tools that follow the standard. In Codex you unzip it into .agents/skills/ in your project, or into ~/.agents/skills/ for all your projects; Codex has supported SKILL.md directly since the open standard of December 2025. Putting the contents of SKILL.md into your AGENTS.md still works too. The instructions themselves are plain readable text, so any assistant that accepts instruction files can handle it.
Does the skill invent retention figures if I do not supply them?
The instructions forbid inventing retention, conversion or usage figures and use [TO BE COMPLETED] for missing current data. They may propose future measurement plans, but those are not already collected results. The skill does not promise a retention percentage. These are static instructions, not proof of a particular model’s runtime compliance.
Does the skill refuse certain products?
Yes. For products that cause harm with heavy use it does not build a loop: gambling, impulse credit, and anything aimed at children or other vulnerable groups. Then it refuses and explains why. It does not recommend dark patterns either, so no hidden cancel buttons, no false scarcity and no notifications that suggest something that is not there.
What is the Manipulation Matrix and why is it in there?
Eyal’s Manipulation Matrix asks whether you would use the product yourself and believe it materially improves users’ lives. Two yes answers describe the Facilitator quadrant, not proof of measured benefit. This skill separately requires a benefit hypothesis, evidence or a measurement plan and an unwanted-use assessment. It checks ethics after context and before Step 2, then repeats Step 7 after synthesis; missing answers remain unknown.
What does the skill need from me to work?
Eight things are in the checklist: what the product does in one sentence, who the user is and what situation they are in during use, the core behaviour, the desired frequency, where users currently drop off and after how many times, which channels are available for triggers, which data the product already collects and may use, and whether there is an existing routine the behaviour can latch onto. It only asks about what is missing.
For which products is the Hook Model not suitable?
The file excludes harmful intensive use and pure acquisition questions, and focuses on recurring short-cycle behaviour rather than occasional tasks such as tax returns or mortgages. It requires a credible user-benefit hypothesis before recommending a loop. Habits can also be unhelpful, so forming one is not evidence of value. The four-stage model is not a measured law.
Get found first, then bring them back
A good loop brings people back, but someone still has to come in first. If the inflow lags behind, the real work sits in front of this page: getting found by the people looking for you, in Google and in AI answers. The free SEO scan shows in a few seconds where your site stands. And if you want to talk through what else AI can do for your business, from individual skills to full automation, we simply do that in a conversation.