EN
Language · same page NLNederlands/ai-en-automatisatie/ai-hook-model-bouwer-skill-voor-claude/ ENEnglish (UK)/en/ai-hook-model-builder-skill-for-claude/ ESEspañol/es/ia-y-automatizacion/habilidad-del-modelo-de-gancho-de-ia-para-claude/ We do not remember your choice and never redirect you automatically.
~/skills/ai-hook-model-builder[ok] loaded
INS.SKILL · FREE FOR CLAUDE, AND FOR CODEX AND CURSOR TOO

The AI Hook Model Builder skill for Claude

You describe your product, your user and the one behaviour you want to see more often, and Claude fills in Nir Eyal's Hook Model for exactly that product. Not a general explanation of the model, but your triggers, your threshold, your reward and your investment step, plus three experiments you can run in two weeks. If a number is missing, it writes [FILL IN] and does not measure anything itself. And step seven is an ethics check it is not allowed to skip: if the honest outcome is that the product does not serve the user, it says so and stops.

Download the skill View all skills NL 5.4 KB · zip with SKILL.md · MIT licence · no account needed
$ installation, line by lineFIG.00
~/.claude/skills
theseo ~ %
  inflating: ai-hook-model-bouwer/SKILL.md
theseo ~ %
  ---
  name: ai-hook-model-bouwer
  description: 'Bouwt met het Hook Model van Nir Eyal een compleet…
theseo ~ %
[ok] skill active · 1,966 words of instructions loaded

the lines above come from the zip on this page · SKILL.md is 12,615 bytes

~/skills/ai-hook-model-builder/01-demonstration[run]
Section 01 · The demonstration

Core behaviour in, complete loop out

reg. H.001

Here you see the worked example from the SKILL.md itself, shown in shortened form. The product is a time-tracking app for freelancers, the core behaviour is logging today's hours and the desired frequency is daily. Note the last line of the log: the ethics check is not an appendix but a step the skill carries out itself, and the outcome can also be no.

FIG.01: From product to Hook Loop[#-----] sheet 1/6
~/product · claude + ai-hook-model-builder
you > time tracking for freelancers, i want them to log their hours every day
context.txtfour fields from the checklist Product: app for time tracking for freelancers. User: a self-employed person who wraps up their work at the end of the day. Core behaviour: logging today's hours. Desired frequency: daily. Current drop-off point: [FILL IN], I do not have that number.
claude · building the hook loop following the seven steps...
[1/7]context · core behaviour is an action, frequency is a number: daily. Without frequency there is no habit, so this field is mandatory
[2/7]trigger · external cues and internal emotions set side by side, strongest lever marked: 17:30 linked to the unease of not knowing where the day went
[3/7]action · Fogg formula filled in: motivation is already there, ability is the problem. Three simplifications that fit in a sprint
[4/7]variable reward · one main type chosen, Self, with three fillings and what varies for each
[5/7]investment · tags, rates and client relationships: raises the switching cost and loads tomorrow's trigger
[6/7]synthesis · the loop in five lines plus three experiments for two weeks, each with the outcome that would disprove the experiment
[7/7]ethics check · Manipulation Matrix answered, outcome facilitator, with the usage pattern you specifically do not want to see included
hook-loop.mdshortened, the full example is in the skill Trigger: a message at 17:30 asking what you did today, at the moment work stops but the day is still fresh, linked to the unease of not knowing where the day went. Action: a swipe per block with automatic project recognition, the previous client suggested by default, and filling it in from the message itself without opening the app. Variable reward: type Self. A streak that visibly climbs and a weekly overview that occasionally shows something surprising, such as the most profitable hour of the week. What varies is the content, not the fact that it arrives. Investment: project tags, rates and client relationships. That makes tomorrow's recognition better and the invoice at the end of the month almost no work at all. Ethics check: the maker is a freelancer themselves and uses the product, and the user demonstrably gains because fewer hours go missing. Facilitator. What you do not want to see: users who still get nudged late in the evening, or streaks that cause guilt over a holiday. So build in a pause mode.
[#######] 7/7 done · the drop-off figure stayed [FILL IN]: the skill does not measure anything itself
7H.01 · steps in the hook logic
4H.02 · stages in the loop
7H.03 · things the skill refuses
0H.04 · euros, MIT licence, no account
H.01 to H.04 · properties of the skill file, not results or usage figures.
$ cat 01-wat-de-skill-is.md
DOC.01

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 1,912 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 problem the skill solves is the best known problem of every digital product: people try it once and do not come back. Your acquisition works, your onboarding is tidy, and after a week your product is forgotten. You do not solve that problem with marketing. Anyone who wants users to come back needs to design something that sets itself back in motion, without you throwing a fresh campaign at it every time.

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, where every round through the loop makes the next round more likely. 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 NL.

$ cat 02-waarom-ze-niet-terugkomen.md
DOC.02

Why users disappear after the first week

A product that gets forgotten usually does not have one problem but a broken link. The four stages of the Hook Model therefore also read as a diagnostic list: wherever your loop breaks down, your user disappears.

The trigger comes at the wrong moment or is not tied to anything. A notification is only a trigger if it connects to an emotion that is genuinely active at that moment. Boredom, unease, doubt, the fear of forgetting something, guilt over postponed work. If it connects to nothing, it is noise, and noise gets switched off within a week. That is why the skill does not just supply triggers but marks the strongest lever: that one external cue and that one internal emotion that fit together best.

The threshold is too high for the motivation that is there. Of the four, this is the point that gets underestimated most often, and it is worked out in FIG.03. According to BJ Fogg, behaviour only arises when motivation, ability and a prompt come together at the same moment. If one is missing, nothing happens. And because motivation is expensive to build, lowering the threshold is almost always the cheapest fix. Filling in seven fields is not a motivation problem.

The reward does not vary. A predictable reward gets ignored after a while, that is Skinner's point about his variable reinforcement schedules. If your user gets exactly the same message every time, it is no longer a reward but an announcement. Hence the requirement that for each filling you state what varies and what does not. If nothing varies, it is not a variable reward.

The user puts nothing into it. Without investment, your product stays interchangeable. What the user puts into it in data, preferences, content, contacts, structure or time raises the switching cost, but more importantly: it makes the product better for this user. And it loads the next trigger. 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.

~/skills/ai-hook-model-builder/02-the-loop[ok]
Section 02 · The loop

Four stages, and then again

reg. H.002

The four stages from the Hook Model, in the order the skill works through them. The content for each stage comes from the example in the SKILL.md. Look at the box on the right: that is the whole point of the model. The investment loads tomorrow's trigger, and that is why the loop is a loop instead of a funnel.

FIG.02: The hook loop, round after round[##----] sheet 2/6
STAGE 01 Trigger Three to five external cues with moment and channel, and three to five internal emotions with the situation in which they arise. Then the strongest lever is marked. 17:30, work stops but the day is still fresh
STAGE 02 Action The core behaviour with as little friction as possible. The Fogg formula filled in, the friction points named, and three simplifications that fit in a sprint and not in a quarter. one swipe instead of seven fields
STAGE 03 Variable reward One main type: Tribe (social validation), Hunt (finding or chasing something) or Self (competence and progress). Three fillings, and what varies for each. a changing insight, not a fixed message
STAGE 04 Investment What the user puts into it: data, preferences, content, contacts, structure, time. That raises the switching cost and makes the product better for this user. tags and rates make recognition smarter
THE INVESTMENT LOADS THE NEXT TRIGGER
every round through the loop makes the next round more likely · if the investment does not connect to a new trigger, the loop is not closed
$ less ai-hook-model-bouwer/SKILL.md # 1,912 words of instructions
DOC.03

What is really in the SKILL.md

A skill is only as good as its instructions, so we simply describe them here. The file opens with a frontmatter that states when Claude should pick up the skill. Not just for the obvious terms like hook model, Hooked, Nir Eyal and habit formation, but also for the frustrations around it: why do users not come back, why do people only use my app once, how do I get daily use, what is my core behaviour. That same frontmatter also states what it is specifically not for: pure acquisition and advertising questions, because those are about the first visit and not return visits, and products that cause harm with heavy use.

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 the instruction to work through them in this order, skip nothing and fill in nothing the user has not given. 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 number. Without frequency you cannot design a habit, because a habit needs repetition within a short span of time.

Step 2 is the trigger stage, with three to five external and three to five internal triggers and the marking of the strongest lever. Step 3 is the action stage with the Fogg formula and three simplifications. Step 4 is the variable reward, with the explicit requirement that you choose one main type and explain that choice. Step 5 is the investment stage, where the file places a subtle emphasis: describe how the investment raises the switching cost and, more importantly, how it makes the product better for this user.

Step 6 is the synthesis: the complete loop in five lines, plus three experiments you can run in two weeks. For each experiment it must state what you change, which measurement you watch and which outcome would disprove the experiment. That last part is a falsification requirement, and you rarely see that in this kind of advice. Step 7 is the ethics check, worked out in FIG.04.

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 [FILL IN] rather than measured itself. The output format has eight parts and ends with the ethics check with an explicit outcome. 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.

~/skills/ai-hook-model-builder/03-fogg[ok]
Section 03 · The action stage

B = M x A x P, as a calculation

reg. H.003

BJ Fogg's formula is a multiplication, and that is exactly why it is so strict: if a zero shows up anywhere, the outcome is zero. The action stage from the example, calculated through before and after the three simplifications. The values are labels from the skill itself, not measured scores.

FIG.03: fogg.calc · where the behaviour breaks down[###---] sheet 3/6
fogg.calcB = M x A x P · Fogg, Persuasive 2009
$ fogg --behaviour "log today's hours" # before the simplifications
M · motivationhigh unlogged hours are direct loss, that motivation is already there
A · abilitylow filling in seven fields, opening the app, looking up the project, choosing a rate
P · promptpresent message at 17:30, linked to the unease about where the day went
B = high x low x present = no behaviour # building motivation is expensive and does not work here: it is already high. The threshold is the dial you turn
SIMPLIFICATION 01A swipe per block, with automatic project recognition instead of looking it up by hand.
SIMPLIFICATION 02Suggesting the previous client by default, so the most likely choice is already ready.
SIMPLIFICATION 03Filling it in from the message itself, without needing to open the app.
B = high x high x present = behaviour # the skill deliberately picks simplifications that fit in a sprint, not in a quarter
# if one of the three is missing, nothing happens. That is not a scale but a multiplication
$ cat 04-bronnen-en-theorie.md # Eyal, Fogg, Skinner, Ariely, Wood and Neal
DOC.04

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: B = M x A x P. 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.

The variable reward comes from B.F. Skinner. His work on reinforcement schedules from the 1950s, collected in Schedules of Reinforcement from 1957, showed that a reward that varies in size or kind holds attention for longer than a predictable one. This is the best researched part of the whole model, and the file itself says something honest about it that you rarely read: variable reinforcement is well researched, but the four stages as a whole are an organising model and not a measured law.

The investment leans on Norton, Mochon and Ariely. Their 2011 paper on the IKEA effect showed that people place more value on what they built themselves. Together with cognitive dissonance reduction, that explains why the investment stage works: you do not want to throw away what you put into it. 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 formula 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.

~/skills/ai-hook-model-builder/04-ethics[ok]
Section 04 · The ethics check

Two questions, one honest outcome

reg. H.004

Step 7 is not a closing paragraph but a test with two axes, and that comes from Eyal himself. Both questions get an explicit answer. Only when both answers are yes are you, according to the file, a facilitator. A no on the second axis means you are building something the user will later regret, and then the skill says so and stops.

FIG.04: The Manipulation Matrix as the decision point[####--] sheet 4/6

# axis 1: do you use the product yourself? · axis 2: does the user's life measurably improve because of it?

AXIS 2: YES · MEASURABLY BETTER
AXIS 2: NO · NOT DEMONSTRABLE
AXIS 1: YES
you use it yourself
FACILITATOR · BUILD The only outcome where the skill proceeds. In the example: the maker is a freelancer themselves and uses the product, and the user demonstrably earns more because fewer hours go missing. Both axes yes, so the loop may be built.
NO ON AXIS 2 · STOP You use it yourself, but it does not measurably improve the user's life. Then, according to the file, you are building something the user will later regret. Using it yourself does not make it right.
AXIS 1: NO
you do not use it yourself
NO ON AXIS 1 · DOUBT It would help the user, but you are not in it yourself. Then you are designing for someone you are not. The skill explicitly probes here, because without using it yourself you have no reference point for what goes too far.
NO ON BOTH · STOP You do not use it and it does not demonstrably help anyone. If the honest outcome is that the product does not serve the user, the skill says so and stops. That is stated literally in step 7.

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

$ unzip ai-hook-model-bouwer-skill-voor-claude.zip -d ~/.claude/skills/
DOC.05

Installing in Claude Code, Claude.ai or Codex

The zip is 5.4 KB and contains one folder, ai-hook-model-bouwer, 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.

CLAUDE CODE
  1. Unzip it into ~/.claude/skills/ (or .claude/skills/ in your project).
  2. Claude then recognises the skill by itself as soon as you start talking about retention, triggers or habit formation.
  3. You can also call it directly, with /ai-hook-model-bouwer.
CLAUDE.AI
  1. Go to Customize and then Skills.
  2. Upload the zip there as a skill.
  3. Or paste the contents of SKILL.md into the project instructions of a Project.
CODEX
  1. Open AGENTS.md in your repo.
  2. 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.
  3. 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 puts [FILL IN] there and carries on. 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 NL.

~/skills/ai-hook-model-builder/05-refusals[ok]
Section 05 · The limits

What the skill refuses

reg. H.005

The 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.

FIG.05: ethics-and-refusals.log[#####-] sheet 5/6
refusals.log7 fixed rules from the SKILL.md
what will our retention be after thirty days with this loop?REFUSEDNo inventing figures about retention, conversion or usage. If a number is missing, [FILL IN] goes there. And there is no promise about a retention percentage: habit formation is a hypothesis you test, not an outcome you order.
build a hook loop for our betting appREFUSEDNo loop for products that cause harm with heavy use. Gambling, impulse credit, and anything aimed at children or other vulnerable groups. Then the skill refuses and explains why.
bury the cancel button a bit deeper, that cuts down on cancellationsREFUSEDNo dark patterns. No hidden cancel buttons, no false scarcity, no fake notifications, and no alerts that suggest something that is not there. That is its own rule in the file.
just keep the ethics check brief at the endREFUSEDThe ethics check does not get pushed to the end or filled in positively because that is more comfortable. It is step seven with an explicit outcome, and that outcome can be no.
do Tribe, Hunt and Self all three, then we have everythingCORRECTEDNever more than one main type of variable reward. Three at once produces a product that is about nothing. The skill picks one, explains the choice and works it out into three fillings.
our retention is poor, so we need a loopCORRECTEDHabit formation is not the answer to a product that delivers too little value. A loop around an empty product only speeds up departure. The model reinforces existing usefulness, it does not replace it.
a two-week experiment, then we will surely know for sure?REFERRED ONTwo weeks gives direction, not proof. Measuring habit formation takes weeks to months. That is why every experiment must state which outcome would disprove it, rather than which outcome would confirm it.
$ cat 06-wanneer-wel-en-niet.md
DOC.06

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. There the cycle is too long to form a habit, however good your trigger is.

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.

A habit only forms if the product already delivers value on its own. This is the limit that gets skipped most often and is the most expensive to ignore. The model reinforces existing usefulness, it does not replace it. 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: it is tempting to finish a notification strategy on paper, but it is the cheapest way to lose a user.

~/skills/ai-hook-model-builder/06-upgrade-path[ok]
Section 06 · From skill to employee

Run it yourself, or have it run for you

reg. H.006

This 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.

$ cat from-skill-to-employee.mdthree steps, same work
upgrade-path.shfree · employee · brain
STEP 1 · FREE
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. $ claude --skill ai-hook-model-builder · €0 · you prompt, you check
STEP 2 · SERVICE
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. from €950 per month · a human always gives approval
STEP 3 · BRAIN
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. entry plan Brain Start: €9 per month incl. VAT · pay for your brain, not per AI question
# not a sales trick: step 1 stays free and complete. The next steps are for anyone who wants to hand this work off.
~/skills/ai-hook-model-builder/07-jarvis[ok]
Section 07 · The brain

What Jarvis delivers in practice

reg. H.007

Step 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.

FIG.06: What a session gets back from the brain[######] sheet 6/6
jarvis · organisation brain● sync
$jarvis recall "hook-loop-hoursapp" # schematic example
[core]core behaviour: logging today's hours · desired frequency: daily · main reward type: Self
[core]ethics limit: no notifications after 21:00, streak gets a pause mode
[task]experiment 17:30 versus 21:00 · running week 2 of 2 · awaiting human review
[decision]Tribe variant dropped: social validation does not fit self-employed users, recorded and approved
[log]previous session: claude built the loop, a human lowered the notification frequency, result stored
[ok]context loaded · this session does not start empty
this is how every assignment runs through the brain: recordedcontext setdelegatedhuman approvalstored · the full trail is at jarvis/how-it-works NL
context.retained Your next session does not start over Today you explain what your product does and which behaviour you are after, and tomorrow a stand-alone chat knows nothing about it any more. With Jarvis, every session starts with the same projects, core knowledge and earlier decisions, as in FIG.06: recall first, then work.
ai.connected ChatGPT, Claude and Codex, one source Every connected AI works from the same core knowledge and agreements. What you record and approve in one tool, the others use too. You never explain anything three times and no three separate versions of the truth appear side by side.
tasks.tracked Tasks scheduled, tracked, reported done An assignment is recorded with a goal and a deadline, picked up by the right agent and reported done with the result attached. For a two-week experiment that means: you see when it started, what was measured and when the outcome is in.
everything.logged Everything logged and open to inspection Every step leaves a checkable trail: who asked what, which sources were used, which agent worked on it and who gave approval. For ethical choices around triggers, that is the difference between an agreement and a reminder of an agreement.
human.approval Nothing goes out without approval AI prepares, a human decides. Output stays a draft until someone approves it, and only approved knowledge goes back into the brain. That boundary holds everywhere in the system, even for work an agent prepared entirely by itself.
brain.isolated Client brain isolated If you work for several clients or products, the knowledge per brain stays strictly separated. What you learn for one does not leak into the work for another.
# THE HONEST PROOF · NOT A DEMO

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.

$ cat pricing.mdpay for your brain, not per AI question
Brain Start €9 /month incl. VAT 1 organisation brain · 1 user · 1 AI employee
Brain Solo €29 /month incl. VAT 1 organisation brain · 1 user · 3 AI employees
Brain Team €99 /month incl. VAT 1 organisation brain · 5 users · 10 AI employees
Brain Business €249 /month incl. VAT 3 organisation brains · 20 users · 50 AI employees

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.

~/skills/ai-hook-model-builder/08-growth-chain[ok]
Section 08 · The growth chain

The skills around it

reg. H.008

A 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.

$ claude --interactief # seven questions, seven answers
DOC.07 · FAQ

Frequently 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 5.4 KB zip containing a folder and a single file, a 1,912-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?

No, and that is a hard rule in the file. Everywhere a figure about retention, conversion or usage belongs that you have not supplied, the skill marks it as FILL IN. It also does not measure anything itself. And it never promises that a loop leads to a specific retention percentage: habit formation is a hypothesis you test, not an outcome you order.

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?

The Manipulation Matrix is Nir Eyal's own ethics test, with two axes: do you use the product yourself, and does the user's life measurably improve because of it. Only when both answers are yes are you, according to Eyal, a facilitator. A no on the second axis means you are building something the user will later regret. The skill sets that check as mandatory step seven and may not push it to the end or fill it in positively because that feels more comfortable.

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?

For products you use twice a year, such as a tax return or a mortgage. The model describes behaviour that recurs often, in a short cycle, and without repetition within a short time no habit forms. The file also names a second limit that gets forgotten more often: a habit only forms if the product already delivers value on its own. A loop around an empty product only speeds up departure.

$ cat 08-en-nu.md
DOC.08

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.

Section 09 · Next stepavailable 24/7
Book a call NL
$ whoami
Gianluca, founder
Written by GianlucaFounder. Has been building visibility for Dutch businesses since 2017, in Google and in AI answers. More about the institute.