drive-motivation
Design motivation systems using Autonomy, Mastery, and Purpose (AMP) for products and teams. Use when the user mentions "intrinsic motivation", "gamification isnt working", "rewards arent working", "autonomy", "mastery", "purpose-driven", "my team is disengaged", or "how do I motivate people". Also trigger when designing onboarding progression, fixing broken gamification, or building team structures that sustain high performance. Covers why carrot-and-stick fails and how to build progress systems. For habit-forming product loops, see hooked-ux. For retention behavior design, see improve-retent
npx skills add wondelai/skills --skill drive-motivation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Drive Motivation Framework Design motivation systems for products, teams, and organizations using the science of intrinsic motivation. ## Core Principle **The secret to high performance isn't rewards and punishment — it's the deeply human need to direct our own lives, learn and create new things, and do better for ourselves and our world.** For any task requiring even rudimentary cognitive effort, external rewards either don't work or actively worsen performance. Intrinsic motivation — Autonomy, Mastery, Purpose (AMP) — drives lasting engagement. ## Scoring **Goal: 10/10.** Score any motivation system (product features, team incentives, gamification, engagement loops) against the [Quick Diagnostic](#quick-diagnostic): start at 5, add 1 for each of the first five rows answered "yes," then **subtract 2 if the sixth row is also "yes"** — an "if-then" reward doing the motivating crowds out the rest. Bands: - **9-10** — autonomy, mastery, and purpose all present; no if-then crowding-out. - **5-6** — one pillar carries the system; the other two are weak or extrinsic. - **≤3** — relies on rewards, mandates, or controlling behaviors; intrinsic motivation absent. Always state the current
- Core Principle
- Scoring
- Motivation 1.0, 2.0, and 3.0
- The Seven Deadly Flaws of Extrinsic Rewards
- The Three Pillars: Autonomy, Mastery, Purpose
- 1. Autonomy
- 2. Mastery
- 3. Purpose
- AMP Applied: Product Design
- Gamification Done Right vs. Wrong
- Team Motivation
- Compensation and Incentives
- Type I vs. Type X Behavior
- Common Mistakes
What does the drive-motivation skill do?
Design motivation systems using Autonomy, Mastery, and Purpose (AMP) for products and teams. Use when the user mentions "intrinsic motivation", "gamification isnt working", "rewards arent working", "autonomy", "mastery", "purpose-driven", "my team is disengaged", or "how do I motivate people". Also trigger when designing onboarding progression, fixing broken gamification, or building team structures that sustain high performance. Covers why carrot-and-stick fails and how to build progress systems. For habit-forming product loops, see hooked-ux. For retention behavior design, see improve-retent
How do I install it?
Run `npx skills add wondelai/skills --skill drive-motivation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From wondelai/skills, a repository with 1,835 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.