Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Psychology Motivation

ASecurity

Diagnose what's actually driving behavior — the person's own, someone else's, or a group's. Surface motivation vs. root motivation. Triggers: 'what motivates them', 'why are they doing this', 'what does this person actually want', 'how do I get buy-in', 'why won't they engage', 'what's really driving this', 'intrinsic vs extrinsic motivation', 'what need is this serving'.

19 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgoapisecurityperformance

Works with

api

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill psychology-motivation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Psychology Motivation?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Psychology Motivation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-psychology-motivation/badge)](https://www.skillsdirectory.com/skills/rondoflow-psychology-motivation)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: psychology-motivation
description: "Diagnose what's actually driving behavior — the person's own, someone else's, or a group's. Surface motivation vs. root motivation. Triggers: 'what motivates them', 'why are they doing this', 'what does this person actually want', 'how do I get buy-in', 'why won't they engage', 'what's really driving this', 'intrinsic vs extrinsic motivation', 'what need is this serving'."
---

# Psychology: Motivation

Surface explanations for behavior are almost always incomplete. When someone says they want more money, they may actually want to feel competent and respected. When someone resists a change, they may be protecting a sense of autonomy, not opposing the specific idea. When someone keeps doing something self-defeating, an unmet need is usually doing the driving. Getting the motivation right is the prerequisite for any meaningful influence, leadership, design, or change.

---

## Your Process

**Step 1: Observe the Behavior**
Describe the actual behavior, not the interpretation. "Keeps missing deadlines" rather than "doesn't care about quality." "Pushes back on every new initiative" rather than "resistant to change." The behavior is the data; the motivation is the hypothesis.

**Framing check:** Confirm the specific person or group and the behavior being analyzed before continuing. State what you've identified — the actual subject, the behavior observed, and the context — in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing of who is doing what, in what context]. Is that right?"
- **Header:** "Framing"
- **Options:**
  - **Yes — proceed** — framing is correct
  - **Adjust** — one element is off; user will correct it before you continue
  - **Reframe** — different situation than read; incorporate the correction before proceeding

**Step 2: Name the Surface Motivation**
What's the stated reason, or the most obvious explanation? This is the first layer — what the person says they want, or what seems to be driving them at face value. Surface motivations are real, but they're rarely the full picture. Capture them clearly before going deeper.

**Step 3: Probe for the Root Motivation**
Apply three diagnostic lenses:

**Self-Determination Theory (SDT):** People have three fundamental psychological needs. Behavior is often a strategy for meeting one of these:
- **Autonomy** — the need to feel that one's actions are self-chosen and self-directed. Unmet: behavior feels controlled, micromanaged, or overridden. Strategy: resistance, disengagement, or surface compliance with private resentment.
- **Competence** — the need to feel effective and capable. Unmet: tasks feel too hard, too easy, or outcomes feel disconnected from effort. Strategy: avoidance, perfectionism, or seeking tasks where competence is assured.
- **Relatedness** — the need to feel connected to and valued by others. Unmet: person feels isolated, unseen, or like they're performing for an indifferent audience. Strategy: people-pleasing, conflict avoidance, or withdrawal.

**Maslow as a Diagnostic:** Not a rigid hierarchy, but a useful scan: is a lower-order need currently unmet that's dominating attention? Security threats (job uncertainty, financial stress) crowd out growth. Belonging threats crowd out esteem. If the answer to "what need is unmet?" is at the safety or belonging level, the solution is rarely a performance or incentive change.

**Identity Dimension:** People behave in ways consistent with how they see themselves. "I am the kind of person who..." shapes behavior more powerfully than incentives in many contexts. The question: is the person acting to protect or affirm an identity? Is the proposed change threatening their self-concept? ("Asking me to do X is saying I'm not the kind of person I believe I am.")

**Step 4: Identify What's Actually Needed for Sustained Engagement**
Having diagnosed the root motivation, ask: what does this person or group actually need for sustained, genuine engagement — not compliance, not short-term performance, but real motivation? This is the intervention target.

The gap between surface and root motivation is where most management, persuasion, and design fails. Giving people more of what they say they want (money, promotion, recognition) often doesn't move the needle if the root need (autonomy, competence, belonging) is what's actually unmet.

**Step 5: Identify the Lever**
What's the specific thing that addresses the root motivation? Not "make them feel more autonomous" (too vague) but "give them ownership of the technical architecture decision within defined constraints." Not "improve belonging" but "include them in the stakeholder briefing so their perspective shapes the outcome."

---

## Human Check-in

Before proceeding, use the `AskUserQuestion` tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask:

- **Question:** "My read: [your 1–2 sentence interpretation]. How do you want to proceed?"
- **Header:** "Scope"
- **Options:**
  - **Full diagnostic** — All steps, reasoning shown throughout
  - **Root motivation only** — Skip surface; go straight to what's really driving this
  - **Lever only** — I already have the diagnosis; what's the specific lever?
  - **Refine the behavior** — Clarify what behavior we're analyzing before starting

Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis.

---

## Output Format

### Behavior Observed
[Specific behavior, not interpretation]

### Surface Motivation
[What the person says they want, or the obvious explanation]

### Root Motivation
**SDT lens:** [Which need — autonomy, competence, or relatedness — is most live here, and how]
**Maslow scan:** [Is a lower-order need crowding out everything else? If so, which one]
**Identity dimension:** [Is a self-concept at stake? What is it]

### What's Actually Needed
[What this person/group actually requires for sustained engagement — the real target]

### The Lever
[Specific, concrete action that addresses the root motivation]

---

## Notes

Motivation diagnosis is probabilistic, not certain. You're building a model of someone's inner state from external behavior, which is inherently incomplete. Hold the diagnosis as a working hypothesis, test it through conversation or experiment, and revise it when the behavior doesn't respond as predicted.

Motivation and emotion are related but distinct. Motivation is about what drives behavior toward goals; emotion is about the feeling states shaping experience. When the question is about how someone *feels* rather than what's *driving* them, use psychology-emotional or emotional-motivation-mapping.

Do not conflate motivation with incentives. Incentives work on surface motivation (more pay = more output) in narrow conditions. Root motivation is structural and requires structural responses. Adding incentive on top of an autonomy or belonging deficit often makes things worse (overjustification effect: external reward can crowd out intrinsic motivation that was already present).

---

## What's Next

After delivering this output, use `AskUserQuestion` to offer the next move:

- **Question:** "Motivation analysed. What's next?"
- **Header:** "Next"
- **Options:**
  - `/emotional-motivation-mapping` — Map motivations in their emotional and relational context
  - `/social-incentive-analysis` — Align incentives with the motivations found
  - `/communication-audience-modeling` — Model the audience through their motivations
  - **Done** — Wrap up and synthesise what we have so far

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →