EN
Language · same page NLNederlands/ai-en-automatisatie/ai-switch-framework-verandercoach-skill-voor-claude/ ENEnglish (UK)/en/ai-switch-framework-change-coach-skill-for-claude/ ESEspañolnot translated yet We do not remember your choice and never redirect you automatically.
About this choice

We only save your display preference in a preference cookie, for up to 180 days on this device. No CRM or advertising data. Your tracking consent stays unchanged. If cookies are blocked, your choice may not be saved.

~/skills/ai-switch-framework-change-coach[ok] loaded
INS.SKILL · FREE FOR CLAUDE, ALSO FOR CODEX AND CURSOR

The AI Switch Framework Change Coach skill for Claude

You describe a change that just won't stick, and the skill designs it from three angles at once: the Rider, who needs direction, the Elephant, who needs feeling, and the Path, which has to make the chosen behaviour easier to carry out. That's Switch, the framework by Chip and Dan Heath. First it gathers your situation, then the three tracks, then a 30-day plan with exactly three actions. Not a list of twenty resolutions you never get round to.

Download the skill ↓ View all skills 5.5 KB · zip with SKILL.md · MIT licence · no account needed
$ installation, line by lineFIG.00
~/.claude/skills
theseo ~ %
  inflating: ai-switch-framework-change-coach/SKILL.md
theseo ~ %
  ---
  name: ai-switch-framework-change-coach
  description: Applies Chip and Dan Heath's Switch Framework to lasting personal, team and organisational change…
theseo ~ %
[ok] skill active · 2,063 words of instructions loaded

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

~/skills/ai-switch-framework-change-coach/01-demonstration[run]
Section 01 · The demonstration

Situation in, three tracks out

reg. S.001

This is a shortened conditional sketch based on the second example in SKILL.md. The literal input does not establish a cause, a feasible target or a meeting schedule. Phase 1 gathers context before advice; proposed actions remain hypotheses until the baseline, quality, workload and constraints are understood.

FIG.01: From complaint to three tracks[#----] sheet 1/5
~/change · claude + ai-switch-framework-change-coach
you > My team works too slowly. I want them to have more urgency.
phase-1.logoutline the situation, five questions maximum What exactly is slow, in behaviour you can see? Which team, precisely? What's the current situation and what have you already tried? What does success look like in three months, in visible behaviour? What deadline are you working towards? Then a brief reflection of what was heard. No judgement, no advice, just understanding.
claude · phase 2, working through the three tracks...
[RIDER]working hypothesis · define observable behaviour; a 24-hour email response and ten-minute standup are proposals to check against roles, working hours and workload
[RIDER]bright spots · which team member is already doing this, and why does it work there
[ELEPHANT]investigate · possible obstacles include fatigue, fear or unclear ownership; none is established by the short input
[ELEPHANT]shrink the change · one bounded pilot; halving a process within two weeks is an illustrative ambition, not a feasible target established by the input
[PATH]tweak the environment · support the same proposed ten-minute standup, not a second meeting; agree duration and consider a useful lead-time dashboard
[PATH]rally the herd · share successes openly so the new behaviour visibly becomes the norm
phase-3.mdthe 30-day plan, three actions 1 Rider action: the postcard plus the first critical move, written down so specifically that a teenager could carry it out. 1 Elephant action: the first shrink the change step that can happen this week already. 1 Path action: the first environmental change that makes the new behaviour the default. Check-in: within seven days, with a measurable success indicator attached.
[###] 3/3 phases done · three focused actions, with necessary safety and quality obligations retained
3S.01 · phases, always in this order
9S.02 · techniques, three per track
5S.03 · things the skill never does
0S.04 · euros, MIT licence, no account
S.01 to S.04 · properties of the skill file, not results or usage figures.
$ cat 01-wat-de-skill-is.md
DOC.01

What the AI Switch Framework Change Coach is

The AI Switch Framework Change Coach is a free skill from our skill library. A skill is an instruction file, SKILL.md, that gives an AI assistant a fixed way of working for a task. No software to install, no subscription, no connection to your systems: a 2,063-word text file that tells Claude how to design a change according to Switch, what order the phases come in, which nine techniques it uses in total, three per track, and what it never does under any circumstance. You download the zip at the top of this page, put it in your Claude environment, and from that moment Claude thinks in Rider, Elephant and Path as soon as you say something needs to change.

Switch offers three angles for exploring a change: direction, motivation and environment. They are questions to investigate together, not an exhaustive explanation of resistance or proof that a change fails after three weeks. The skill keeps all three in view without diagnosing people from a short request.

This skill is written for anyone who needs to get something moving without having authority over it, or who has the authority and still no result: business owners pivoting their company, leaders who need to change culture, teams stuck in old patterns, and people who want to change a personal habit. Together with the rest of the skill library, we make it available for free from our AI and automation service, with no account and no sales email afterwards.

The file asks for context before advice. It covers five topics and uses information already supplied instead of repeating questions. Three months is an illustrative horizon; the actual deadline is agreed with the user. The prompt does not guarantee the quality or outcome of an AI response.

$ cat 02-waarom-verandering-stilvalt.md
DOC.02

Why change can stall

The Heath brothers use Jonathan Haidt’s Rider and Elephant metaphor, with the Path representing the environment. The Rider stands for planning and analysis; the six-tonne Elephant illustrates emotion and motivation. It is an organising metaphor, not a literal model of the brain, a clinical diagnosis or a measurement of why a particular person has not acted.

Explore whether direction is clear. The first track asks about observable behaviour, useful bright spots and a concrete destination. Ambiguity can make action harder, but it does not establish the cause of a person’s delay. Script the Critical Moves turns an abstract aim into a proposed behaviour that can be discussed and tested.

Explore motivation alongside the plan. Feelings, energy and identity may matter, but tiredness or fear must not be assumed. The techniques invite a meaningful connection, a small first step and opportunities to learn. A first success within a week is something to assess, not a promised result.

Examine the environment. Physical or digital arrangements, routines and voluntary peer support may make a chosen behaviour easier. They do not guarantee success, and reliance on willpower does not by itself establish failure. Any dashboard, meeting or other cue should fit the actual situation.

The workflow considers Rider, Elephant and Path together. This is a coverage rule for designing a plan, not proof of why most organisations or changes fail. The analysis remains provisional and should make other constraints, missing facts and uncertainty visible.

In diff form, with lines pointing to the examples in the skill: what goes out and what comes back in its place.

~/skills/ai-switch-framework-change-coach/02-three-tracks[ok]
Section 02 · The three tracks

Rider, Elephant, Path

reg. S.002

Phase 2 explores each track through questions, a provisional working hypothesis and three to five candidate actions. These are options, not simultaneous commitments. There are nine techniques in total, three per track. Phase 3 selects one final action per track; considering all three does not guarantee that a change succeeds.

FIG.02: The three tracks and their nine techniques[##---] sheet 2/5
phase-2.three-tracksdiagnosis, actions, leverage point
TRACK 1 The Rider direct the Rider · the mind DIAGNOSIS Explore whether direction is unclear without diagnosing a cause or labelling a person. Clarify observable behaviour. Does everyone know exactly what behaviour is expected, or is it abstract? Are there bright spots, cases where it's already working that you can copy? Is the end goal visible enough, a postcard from the future? THREE TECHNIQUES Find the Bright Spots. Look for the exceptions where it's already working and analyse why. Script the Critical Moves. Describe the desired behaviour so specifically that a teenager could carry it out. Point to the Destination. Sketch a postcard, concrete enough that people can see it.
TRACK 2 The Elephant motivate the Elephant · the feeling DIAGNOSIS Explore motivation, feelings and identity alongside the plan. Tiredness and fear are possible factors, not assumptions. Does the person or team actually feel anything about this change? Is a credible first success possible within a week? Does the new behaviour fit who someone wants to be? THREE TECHNIQUES Find the Feeling. Make it emotionally concrete, not with numbers but with stories, images and experiences. Shrink the Change. Break the change into steps so small the Elephant isn't afraid of them. Grow Your People. Build a growth mindset: I can learn this works better than I have to be able to do this.
TRACK 3 The Path shape the Path · the environment DIAGNOSIS Investigate environmental support without claiming that willpower fails or the environment guarantees success. Which environmental factors currently make the old behaviour easier? Which habits can you repeat until they become automatic? Which peer pressure works against you or for you? THREE TECHNIQUES Tweak the Environment. Change the physical or digital environment so the new behaviour becomes the default. Build Habits. Link the behaviour to a fixed trigger or routine. Rally the Herd. Use truthful examples and voluntary peer support, without invented proof or coercive pressure.
the order isn't optional: Rider → Elephant → Path · consider all three as a workflow rule, not proof of why most changes fail
$ less ai-switch-framework-change-coach/SKILL.md # 2,063 words of instructions
DOC.03

What's actually in the SKILL.md

A skill is only as good as its instructions, so we simply describe them here. At the top is the frontmatter: the name ai-switch-framework-change-coach, version 1.0.0, MIT licence, and a compact description. The full original trigger list remains in the opening body text. Alongside the term switch framework and the names Chip Heath and Dan Heath, it's mostly made up of ordinary sentences: I need to change, the team won't come along, I can't get moving, why doesn't change stick, I've been trying this for months, and the sharpest of them all, I know what I should do but I don't do it. Those phrases are matching instructions, not a guarantee that a particular assistant will activate the skill.

The file credits the Rider and Elephant metaphor to Jonathan Haidt and describes the Heath brothers’ framework around the Rider, Elephant and Path. It invites investigation of direction, motivation and environment without claiming these explain almost all resistance or delay. The metaphor is not a diagnosis of a person.

Remarkably, it also states when it should not trigger, which is rare for an instruction file. Not when someone is already in the middle of execution and just needs tactical help. Not for a one-off decision. And not for a conflict in a specific conversation. For that last case, the file points to a negotiation technique, and in our library that's the Negotiator skill.

The method itself is fixed in three phases, in this exact order, because they reinforce one another. Phase 1 is outlining the situation with a maximum of five sharp questions: what change, as concretely as possible in behaviour; who needs to change; what's the current situation and what's already been tried; what does success look like in three months in visible behaviour; and what deadline you're working towards. Then comes a brief reflection, without judgement and without advice. Phase 2 is the three-track analysis shown above in FIG.02. Phase 3 is the 30-day plan.

The writing chapter has six rules: British English unless the user explicitly writes in another language; no lists of more than five items; explain jargon; avoid empty management language such as synergy and alignment; address the reader as you; and be direct without being bossy. The English download does not instruct the assistant to answer in Dutch.

At the end are the sources the skill is allowed to cite and the five things it never does. Those five refusals get their own figure further down this page, because they say more about the quality of the advice than the techniques themselves.

~/skills/ai-switch-framework-change-coach/03-30-day-plan[ok]
Section 03 · The action plan

Three actions, thirty days

reg. S.003

Phase 3 selects exactly three final actions, one per track, from the Phase 2 options. It adds a check-in within seven days and a measurable indicator. Three is the plan format, not a claim that a fixed number of actions overrides necessary safety, quality or other obligations.

FIG.03: The 30-day plan[###--] sheet 3/5
$ switch --plan 30dschematic example, built from the examples in the SKILL.md
ACTION 1 · RIDER The postcard plus the first critical move Agree an observable behaviour. A 24-hour email response or Monday shopping is a proposal, not a target supplied by the input or a universal standard.
ACTION 2 · ELEPHANT The first shrink the change step that can happen this week Choose a small step worth trying. Halving a process in two weeks needs baseline and feasibility checks; the original sugar schedule is unvalidated and is not dietary advice.
ACTION 3 · PATH The environmental change that makes the new behaviour the default Explore suitable support. The team may trial one agreed meeting or a useful dashboard; the personal example chooses a preparation cue suited to the user’s needs.
The check-in within seven daysThe seven-day review is a planning checkpoint, not evidence that changes inevitably fail in their first week. Use it to inspect feasibility, effects and needed adjustments.
The measurable success indicatorA number or a visible behaviour you can check after 30 days to see whether it happened. The skill doesn't fill in that number itself and doesn't invent a target for it: you decide what you measure and what counts as good enough.
the timeline depicts the start, review within seven days and 30-day horizon; examples are conditional proposals, not measured projects
$ cat 04-bronnen-en-theorie.md # Heath, Haidt, and the related titles
DOC.04

The theory the skill rests on

The SKILL.md has a separate chapter listing the sources the skill is allowed to cite, and that's deliberate: it lets you check them yourself and decide whether you agree.

The main source is Switch itself. Switch: How to Change Things When Change Is Hard, by Chip Heath and Dan Heath, published in 2010 by Crown Business. The book isn't a theoretical work but a collection of cases where change did succeed, organised along the three tracks. That also explains the shape of the skill: not a model to fill in, but a series of questions that force you to come up with something concrete for each track.

The metaphor comes from Jonathan Haidt. The Happiness Hypothesis, published in 2006 by Basic Books, introduced the Rider on the Elephant as an image for the relationship between the rational and emotional parts of the mind. The skill explicitly credits the metaphor to Haidt rather than the Heath brothers, which is more accurate than what most summaries online say. The Heath brothers' addition is the Path: the environment as a third lever alongside reason and feeling.

The skill may cite the related titles, not parrot them. Four books are listed that you don't need to read but that it's allowed to mention: Made to Stick from 2007, Decisive from 2013 and The Power of Moments from 2017, all three by the Heath brothers, plus Thinking, Fast and Slow by Daniel Kahneman from 2011. If you want to apply the first of those four directly, there's a separate Made to Stick Coach skill that makes messages sticky, which comes in handy precisely for the Elephant track.

Even without installing the skill, you can take apart any stuck change with these three questions: is the direction concrete enough, does anyone feel anything about it, and does the environment make the new behaviour easier than the old one. If you want to look at the same question through a different model, the Fogg Behaviour Model Coach skill splits behaviour into motivation, ability and trigger, and the Atomic Habits Coach skill works the Path track out into a system of habits.

~/skills/ai-switch-framework-change-coach/04-refusals[ok]
Section 04 · The boundaries

What the skill never does

reg. S.004

The SKILL.md closes with five things the skill never does, and all five are about the quality of the advice rather than safety. Which makes sense: for a change coach, bad advice is the real risk. In conversation those rules play out like this: each rule is a request you might make, together with the response the skill gives according to its own instructions.

FIG.04: refusals.log[####-] sheet 4/5
refusals.log5 fixed rules from the SKILL.md
skip those questions and just give me your advice straight awayREFUSEDNever start giving advice before you've gathered the situation. Phase 1 isn't optional. Without knowing who needs to change, what's already been tried and what success looks like in visible behaviour, any advice is a gamble with your month as the stake.
run my pricing through Rider, Elephant and Path too while you're at itCORRECTEDNever just stick Switch terminology onto a question that isn't about change. A framework that fits everything explains nothing. The skill would rather say this isn't a change question than invent an Elephant for it.
I just want the plan, skip the feelings partREFUSEDNever do Rider without Elephant and Path. This is a coverage rule for the workflow. It is not an established explanation of why most changes fail or a prediction of a three-week relapse.
give me twenty actions, I'll pick the ones I want myselfREFUSEDNever give a list of twenty actions, pick the sharpest three. Phase 2 offers candidate options; these are not all commitments or a diagnosis of procrastination. Phase 3 therefore delivers exactly one action per track.
tell my colleague he should just want thisCORRECTEDNever be moralistic about what someone should want. The skill asks what's underneath the behaviour, then looks for a path that fits who someone wants to be. Moralising makes the Elephant dig in, and you don't move an Elephant that's dug in.
$ unzip ai-switch-framework-change-coach-skill-for-claude.zip -d ~/.claude/skills/
DOC.05

Installing in Claude Code, Claude.ai or Codex

The zip contains a folder, ai-switch-framework-change-coach, with the SKILL.md inside it. Installing is simply a matter of putting that 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're 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 automatically as soon as you start talking about change, habits, or a team that isn't keeping up.
  3. Start Claude Code with claude, then enter /ai-switch-framework-change-coach inside the session.
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 place SKILL.md alongside it as a separate file and refer to it from AGENTS.md.
  3. Codex reads that along with every session.

After that, using it is simple: describe the change you want to make and answer the phase 1 questions honestly, including the question of what you've already tried. Those failed attempts are especially useful, because they may reveal constraints, assumptions or approaches worth revisiting. If you're new to this kind of file, read what Claude skills are NL first and then how to install Claude skills NL. If you want to write one yourself, for example for the changes that keep recurring in your organisation, writing a SKILL.md NL explains how to go about it.

$ cat 06-wanneer-wel-en-niet.md
DOC.06

When to use it, and when not to

The trigger list includes personal habits, stalled teams, culture changes and business pivots. These situations may involve missing knowledge, resources, conflicting priorities or other constraints as well as difficulty taking action. The first phase investigates the circumstances instead of assuming a shared cause.

The skill is just as clear about when not to use it, and there are three situations. The first: you're already in the middle of execution and just need tactical help. Then targeted help may be more appropriate than a full change plan. The second: it's a one-off decision. A choice between two options isn't a change project, the file points to WRAP Decision Maker. Another tool for examining a proposed plan is the Pre-mortem Analyst skill, which lets a plan fail in advance to see where it breaks. The third: it's a conflict in a specific conversation. For that, the file points to Negotiator. A different conversation tool available in the library is the Nonviolent Communication Coach skill.

The five intake topics help make the situation concrete: desired behaviour, people involved, current state and earlier attempts, observable success and timing. Questions are not meant to establish that a user is uncomfortable or deficient. Use known facts, clarify important gaps and agree a realistic horizon.

Switch is a structure for designing and testing change, not a guarantee or a measured increase in success rates for this prompt. It remains possible that the proposed direction is unsuitable or the team has valid objections. Intake and review should leave room to change the goal or stop an inappropriate intervention.

~/skills/ai-switch-framework-change-coach/05-upgrade-path[ok]
Section 05 · From skill to AI worker

Run it yourself, or have it run for you

reg. S.005

This skill is the free do-it-yourself version of work we also deliver as a service. It stays complete and with no catches, but be aware what a skill actually is: it teaches your AI how to do something, while every new session starts empty. A skill is neither the engine nor the memory. In a 30-day change project you feel that straight away, because you have to explain what happened in week one all over again every session. Anyone who wants it differently has two follow-up steps: hand off the engine, or sort out the memory.

$ cat from-skill-to-ai-worker.mdthree steps, same work
upgrade-path.shfree · AI worker · brain
STEP 1 · FREE
where you are now
The skill: you're the engine You run the Switch Change Coach yourself in Claude, Codex or Cursor. Costs nothing, works today, and you keep it entirely in your own hands: no trial period, no gated parts. The limit is your own time: it only happens when you prompt, and you have to remember the check-in on day seven yourself. $ claude · then /ai-switch-framework-change-coach inside the session · €0 · you prompt, you control
STEP 2 · SERVICE
have it prepared for you
The AI worker: it's ready without you having to prompt Exactly this work, but as a service: an AI worker prepares recurring work without you having to sit behind Claude for it. Control stays with you, because the output stays a draft until a human gives approval. We deliver this through Mansotti, the company TheSEO trades under, which builds the Quote Worker, the Sales Worker and the Reporting Worker. For a change project, the Reporting Worker is the most useful of the three, because it produces the weekly and monthly reports that show you whether the new behaviour is actually happening. from €950 per month · a human always gives approval
STEP 3 · BRAIN
everything from one source
Jarvis: all your AI's work from the same company knowledge The skill teaches the AI, the brain is where the memory lives. Want all your AI's to work from the same company knowledge: that's Jarvis, the organisational brain. It connects ChatGPT, Claude, Codex and your people to the same projects, core knowledge and decisions, so your next AI session doesn't start from scratch. Jarvis selects context, delegates work and only stores what's been approved: client knowledge stays isolated and every step leaves an auditable trail. For a change running over 30 days, that's the difference between a plan and a project. What that means in practice, from the plans to your first week, you can read under Jarvis itself. entry-level Brain Start: €9 per month incl. VAT · pay for your brain, not per AI query
# no marketing trick: step 1 stays free and complete. The next steps are there for anyone who wants to hand this work off.
~/skills/ai-switch-framework-change-coach/06-jarvis[ok]
Section 06 · The brain

What Jarvis delivers in practice

reg. S.006

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 organisational brain: it remembers what your AI's need to know, distributes the work and keeps track of what happened. With change, that's the most sensitive point of all, because a 30-day project consists of sessions that need to know each other. Here's what a new session gets back.

FIG.05: What a change session gets back from the brain[#####] sheet 5/5
jarvis · organisational brain● sync
$jarvis recall "change-project-lead-time" # schematic example
[core]desired behaviour recorded: email within 24 hours, ten-minute standup at nine
[core]bright spot: one team member is already doing this, method written out and shared
[task]check-in day 7 · scheduled · success indicator set before the start
[decision]elephant action scaled down after week 1, halving a process turned out too big: recorded after review, approved by a human
[log]previous session: claude proposed three actions, a human replaced the path action, reason saved
[ok]context loaded · this session doesn't start empty
this is how every task moves through the brain: recorded → context set → delegated → human approval → saved · the full trail is at jarvis/werking
context.retained Your next session doesn't start from scratch Today you explain your team, your goal and your first three actions, and tomorrow a standalone chat knows nothing about it any more. With Jarvis, every session starts with the same projects, core knowledge and earlier decisions, as shown in FIG.05: recall first, only 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.
tasks.tracked Tasks scheduled, tracked, marked complete A task is recorded with a goal and a deadline, picked up by the right agent and marked complete along with the result. The check-in on day seven then isn't a good intention but a task that comes back round.
everything.logged Everything logged and visible Every step leaves an auditable trail: who asked what, which sources were used, which agent worked on it and who approved it. When a change doesn't succeed, that trail can help review the evidence and decisions without assuming a skipped track caused the outcome.
human.approval Nothing goes out without approval AI prepares, a human decides. Output stays a draft until someone approves it, and only approved knowledge feeds back into the brain. For text about colleagues' behaviour, that isn't a luxury but the only defensible way to work.
brain.isolated Client brain isolated If you work for multiple clients, knowledge stays strictly separated per client. What you learn for one doesn't leak into the work for another.
# THE HONEST PROOF · NOT A DEMO

We've been working this way ourselves for months. Every agent session, every task and every decision goes into the log and can be read back. A new session therefore doesn't start blank: it first retrieves the recorded decisions, the running projects and the latest changes, and carries on where the previous one stopped. For a 30-day project, that's precisely the part that usually goes wrong: week three, when nobody remembers any more what was agreed in week one. So not a promise, but the way we work every day.

$ cat pricing.mdpay for your brain, not per AI query
Brain Start €9 /mo incl. VAT 1 organisational brain · 1 user · 1 AI worker
Brain Solo €29 /mo incl. VAT 1 organisational brain · 1 user · 3 AI workers
Brain Team €99 /mo incl. VAT 1 organisational brain · 5 users · 10 AI workers
Brain Business €249 /mo incl. VAT 3 organisational brains · 20 users · 50 AI workers

See all four plans at jarvis/prijzen NL. Through the waiting list NL, you simply pass on your preferred plan, without obligation. That doesn't create an account, an order or a payment obligation. We discuss business customisation first.

~/skills/ai-switch-framework-change-coach/07-related-skills[ok]
Section 07 · Change support

The skills around it

reg. S.007

Switch is one of several behaviour and change models in the library. Their emphases differ and may overlap; the right choice depends on the question and context.

The other change models

same question, different lens

Switch looks at reason, feeling and environment all at once. These two look at individual behaviour and at the organisation.

Fogg Behaviour Model CoachSplits behaviour into motivation, ability and trigger, and shows whether it's about wanting to or being able to.SKILL Kotter Change CoachChange that has to move through an entire organisation, with urgency, coalition and visible early wins.SKILL
$ claude # seven questions, seven answers
DOC.07 · FAQ

Frequently asked questions

What does the AI Switch Framework Change Coach skill cost?

Nothing. It's free, the frontmatter of the file states the MIT licence, and you don't need to create an account or leave an email address. You download a 5.5 KB zip containing the folder ai-switch-framework-change-coach and a single file, SKILL.md, 2,063 words long. That's the complete skill. There's no paid version and no sales email follows.

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 are just readable text, so any assistant that accepts instruction files can work with it.

What are the Rider, the Elephant and the Path?

Rider, Elephant and Path are parts of an organising metaphor: planning and analysis, emotion and motivation, and the surrounding environment. The six-tonne Elephant is illustrative, not a brain measurement or clinical diagnosis. The Rider and Elephant come from Jonathan Haidt’s The Happiness Hypothesis; the Heath brothers use them in Switch alongside the Path.

How many phases does the skill go through?

Three phases, in order: clarify the situation through up to five questions while using facts already supplied; explore three tracks with provisional hypotheses and three to five candidate actions each; then select a 30-day plan with one Rider, one Elephant and one Path action. The plan includes a review within seven days and an agreed measurable indicator. Candidate actions are not all simultaneous commitments.

What techniques are in the three tracks?

Nine, three per track. For the Rider: Find the Bright Spots, Script the Critical Moves and Point to the Destination. For the Elephant: Find the Feeling, Shrink the Change and Grow Your People. For the Path: Tweak the Environment, Build Habits and Rally the Herd. It builds the concrete actions per track on these nine, and picks a few per situation rather than ticking all of them off.

What does the skill never do?

The five rules are to gather the situation before advice, reserve Switch terminology for change questions, consider Rider with Elephant and Path, select three final actions rather than turning the analysis options into a long commitment list, and avoid moralising about what someone should want. These are workflow rules, not proof of why most changes fail.

When isn't this skill the right choice?

Three situations are named in which the skill shouldn't trigger. If you're already in the middle of execution and just need tactical help. If it's purely a one-off decision. And if it's about a conflict in a specific conversation, because then a conversation technique helps you more than a change plan. The Negotiator skill from the same library is meant for that last case.

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

Change inside, visibility outside

A change inside your business only helps if there's something to show for it on the outside. If the flow of new business is drying up, the real work isn't more urgency in the team but being found by the people looking for you. The free SEO scan shows in a few seconds where your site stands. If this kind of thinking works for you, take a look at what else is ready in the library of 100 free skills we make available with no account needed. And if you want to talk further about what else AI can do for your business, from individual skills to full automation, we're happy to do that in a conversation.

Section 08 · 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.