Individual skill
s4h-psychology-motivation
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'.
skills/s4h-psychology-motivation/SKILL.md
Source commit a30df8b67698ccb03ef5e35d68c2eddc5321ad3f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 241
- Repository last updated
- Jul 15, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- claude-code-plugin Repository topic
- cognitive-frameworks Repository topic
- creativity Repository topic
- decision-making Repository topic
- ethics Repository topic
- mental-models Repository topic
- problem-solving Repository topic
- reasoning Repository topic
- systems-thinking Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,740 bytes
Read excerpt
# 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"