Drive Motivation
Intrinsic motivation: Autonomy, Mastery, Purpose
Design for intrinsic motivation using Daniel Pink's research on Autonomy, Mastery, and Purpose. This skill helps your AI agent create features, team structures, and experiences that tap into what truly drives human behavior.
npx skills add wondelai/skills/drive-motivation --global 
Drive Daniel Pink View on Amazon
02 What it is
What is the Drive Motivation skill?
Drive Motivation packages Daniel Pink’s Drive for AI agents, because carrots and sticks degrade performance on any work that requires thought. Your agent audits incentives, goals, and reviews against autonomy, mastery, and purpose, then redesigns the if-then rewards that are quietly crowding out the motivation people already brought with them.
03 Key concepts
Five principles your agent applies.
Drawn from Drive — not advice it repeats back to you, but decisions it makes while it works.
04 Fit
When to use it, and
when not to.
four symptoms it fixes, and four it doesn't.
Reach for it when
You added a bonus to lift performance, and the work got narrower, more gamed, and no better.
Your strongest person stopped volunteering for anything, and nothing about their compensation explains it.
Every task arrives with the method prescribed, and people have stopped bringing their own approach.
You are designing streaks, points, or progress bars and want them to survive the novelty wearing off.
Reach for something else when
Someone is in the wrong seat rather than on the wrong incentive scheme. Traction EOS has the accountability chart.
The team is drowning in domains it should never have owned. Team Topologies calls that cognitive load.
You need the 1:1s and delegation that surface disengagement early. High Output Management is the manual.
You want triggers and variable rewards inside a product. Hooked UX is the sharper tool for mechanics.
05 Prompts
Say it like this.
Name the skill at the end of a prompt and the agent applies the framework rather than a vibe. Or say nothing — it loads on its own when a task matches.
Design a gamification system based on intrinsic motivation, not just points using drive-motivation skill
Create a progress dashboard that supports mastery motivation using drive-motivation skill
Restructure our team to increase autonomy while maintaining alignment using drive-motivation skill
Write onboarding copy that connects users to purpose, not just features using drive-motivation skill
06 About the author
07 Same stack
The stack it sits in.
Four Team & Operations skills. Most people run two: this one, and whichever fits the next problem.
All Team & Operations skills08 Questions
Before you install.
How do I install the Drive Motivation skill?
Run npx skills add wondelai/skills/drive-motivation --global. It takes about 30 seconds and needs no account. The Drive Motivation skill then works in Claude, Claude Code, Claude Cowork, Codex, Cursor, OpenClaw and Hermes Agent — anything that reads the open agentskills.io format — and your agent loads it on its own when a task calls for it. It is free and MIT-licensed, and the source is at https://github.com/wondelai/skills.
Which book is the Drive Motivation skill based on?
It packages Drive by Daniel Pink — five-time NYT bestselling author, former White House speechwriter. The skill distils the book's method into instructions your agent follows while it works, covering autonomy, mastery and purpose. It sits in the Team & Operations part of the library.
Does Drive say I shouldn’t pay people well?
The opposite. Pink’s instruction is to pay enough to take the issue of money off the table — fair and ideally above market — so compensation stops being what people think about. The narrower claim is about contingent if-then rewards dangled in advance, which reliably damage performance on work requiring judgement. Unexpected now-that recognition after the fact delivers the appreciation without the gaming, because nobody could optimise for it.
How is this different from the Hooked UX skill?
Drive explains why someone keeps doing something when nobody is watching; Hooked engineers the loop that gets them back tomorrow. Use this skill on the reward structures, goals, and reviews around human effort — and on product mechanics that need to hold up after the novelty fades, which is where most points-and-badges systems collapse. Use Hooked UX when you want the trigger, action, variable reward, and investment cycle designed explicitly.
Is reading Drive necessary?
Not to apply it — the skill carries the autonomy/mastery/purpose audit, the four T’s of autonomy, the Goldilocks calibration, and the reward rules. The book matters when you have to win an argument: it walks through the experiments, including the candle problem, that show incentives backfiring on exactly the tasks managers most want to accelerate. That evidence is what changes a sceptical CFO’s mind about killing a bonus scheme.
Are there cases where if-then rewards do work?
Yes, and the book is clear about it: for routine, algorithmic tasks with a defined path and little creative demand, contingent rewards are fine and sometimes necessary. The failure mode is applying them to heuristic work — design, engineering, research, sales that requires reading a person. Autonomy also has real limits in safety-critical and regulated work, and the skill will overreach if you don’t tell it about those constraints.
09 Guides that use it
Put it to work.
Long-form playbooks where this skill does part of the job.
One skill, one command.
Install Drive Motivation, or the whole stack.
npx skills add wondelai/skills/drive-motivation --global MIT licensed · Claude, Claude Code, Codex, Cursor, OpenClaw, Hermes · No account