Game Design Player Motivation Audit

Audit a game, feature, live-ops system, progression loop, social feature, or monetization surface using a Self-Determination Theory-inspired motivation frame...

Security Scan

This is an instruction-only skill that provides a Self-Determination Theory-based framework for auditing player motivation; its requirements and instructions are consistent with that purpose and it requests no extra access or installs.

Purpose & Capability

The name and description match the SKILL.md: the skill is an audit framework for game design and motivation. It requires no binaries, credentials, or config paths that would be unrelated to its stated purpose.

Instruction Scope

The SKILL.md contains guidance for performing motivation audits (steps, checks, outputs). It does not instruct the agent to read system files, environment variables, or exfiltrate data. The instructions are design-focused and do not grant broad discretionary data collection.

Install Mechanism

There is no install spec and no code files; this is instruction-only, so nothing is written to disk or installed at runtime.

Credentials

The skill declares no required environment variables, credentials, or config paths. There is no apparent need for secrets or external service access to perform these audits.

Persistence & Privilege

Flags like always or autonomous invocation are default/false; the skill does not request persistent system presence or elevated privileges and does not modify other skills or system configuration.

Assessment

This skill is coherent and low-risk because it is instruction-only and asks for no credentials or installs. Before installing, consider: (1) if you plan to feed sensitive telemetry or player PII into the skill, avoid doing so or sanitize the data; (2) review the full SKILL.md content yourself to confirm it matches your ethical standards (it can be used to optimize monetization or engagement strategies that may have ethical implications); and (3) if you integrate it into an agent with broader permissions, ensure that agent is constrained so it cannot access unrelated secrets or external endpoints when running the audit.

Audit a design by asking not just whether it motivates action, but what kind of motivation it creates, for whom, and at what cost.

Use this skill to distinguish between engagement driven by enjoyment, value endorsement, identity, social pressure, reward dependency, or helplessness. Keep the analysis practical and design-facing, but use terminology that stays broadly consistent with Self-Determination Theory.

Core principle

Not all motivation is equal.

Two designs may generate similar engagement numbers while creating very different player experiences. One may be driven by genuine enjoyment. Another may be driven by reward compulsion, social pressure, or fear of missing out. This skill helps distinguish those motivational structures.

Motivation spectrum

Audit designs across the following motivation types:

1. Amotivation
2. External Regulation
3. Introjected Regulation
4. Identified Regulation
5. Integrated Regulation
6. Intrinsic Motivation

These are not mutually exclusive. Strong game systems often combine several.

What to produce

Generate a motivation audit with these outputs:

1. Target behavior - what the design is trying to motivate
2. Motivation breakdown - which types of motivation are doing the work
3. Need satisfaction check - autonomy, competence, relatedness
4. Motivational profile - the overall mix and likely player effect
5. Diagnosis - how the experience is likely to feel
6. Recommendations - what to strengthen, reduce, or rebalance

Process

1. Define the target behavior

Clarify the behavior the design is trying to produce.

Examples:

• start a session
• complete first 3 actions
• return later in the day
• finish an event track
• engage with social systems
• optimize city layout
• master a mechanic
• collect themed content
• spend premium currency

Write:

• Design being audited
• Target player behavior
• Time horizon - immediate / short-term / medium-term / long-term
• Primary player segment

2. Audit for amotivation

Ask where the design may create helplessness, meaninglessness, confusion, or low-agency compliance.

Amotivation is the failure state. It appears when actions feel empty, forced, over-scripted, or detached from perceived value.

Signals:

• player taps because the UI tells them to, not because they care
• grind without meaningful context
• tutorials or flows that feel like chasing arrows
• actions with low perceived agency
• delays or chores with no emotional or strategic meaning
• story, prompts, or task lists that feel like friction rather than invitation

Ask:

• Does the player understand why this action matters?
• Does the action feel voluntary or merely demanded?
• Does the player feel capable of affecting the outcome?
• Is any part of the flow just "push button to continue"?
• Is the action connected to a player goal, fantasy, or meaningful payoff?

Write:

• Amotivation risks

3. Audit external regulation

Ask how much of the design relies on rewards, punishments, reminders, deadlines, or pressure external to the activity itself.

This is the classic "do X to get Y" layer. It is common in free-to-play systems and often useful for activation, but dangerous when it carries the whole design.

Typical patterns:

• event track milestones
• login rewards
• reward ladders
• timed offers
• battle pass tasks
• grind gates with attractive rewards
• loss aversion and FOMO structures

Ask:

• If the reward disappeared, would the action still be attractive?
• Is the reward carrying the whole system?
• Is the system sustainable, or will it feel hollow once novelty fades?
• Is the reward structure clear and fair?
• Is there a risk of converting play into chore behavior?

Write:

• External regulation drivers

4. Audit introjected regulation

Ask where the design taps into ego, validation, self-image, pride, shame avoidance, status, or social comparison.

This layer is about internal pressure: proving something, keeping up, avoiding embarrassment, preserving self-image, or feeling recognized.

Typical patterns:

• leaderboards
• ranks
• badges and medals
• rare visible rewards
• progression prestige markers
• guild contribution surfaces
• public completion proofs
• comparative map or avatar placement

Ask:

• Does this design create bragging rights?
• Does it create pressure to keep up with others?
• Is social comparison a core driver here?
• Does it encourage pride in participation, or anxiety about falling behind?
• Who benefits from this layer, and who is demotivated by it?

Write:

• Introjected regulation drivers

5. Audit identified regulation

Ask where the design helps players consciously endorse the value of the activity, even if the action itself is not always the most fun moment-to-moment.

This is where the player believes the activity matters and accepts it as worthwhile.

Typical patterns:

• helping a club or team
• maintaining a city or social ecosystem
• contributing to a long-term build
• performing support roles
• doing tedious actions because they matter to a bigger goal
• completing systems because the player values what they represent

Ask:

• Does the player feel this action matters beyond the immediate reward?
• Is there a larger purpose attached to the task?
• Does the design create a feeling of contribution?
• Are players consciously buying into the value of the action?
• Does the action support a long-range project, group, or personally meaningful goal?

Write:

• Identified regulation drivers

6. Audit integrated regulation

Ask whether the activity can become part of the player's identity, self-concept, or ongoing role.

This is a deeper layer of internalization. The player no longer just values the activity; they see it as part of who they are.

Typical patterns:

• specialized playstyles
• creative mastery communities
• collector identities
• highly expressive builds or loadouts
• role ownership within social groups
• long-term hobbyist subsystems
• deep feature ecosystems with room for expertise

Ask:

• Can a player say "I am the kind of player who does this"?
• Does the system support long-term self-expression?
• Does it reward specialization and ownership?
• Can players build identity, reputation, or belonging around it?
• Would superfans form around this system?

Write:

• Integrated regulation drivers

7. Audit intrinsic motivation

Ask whether the activity itself is enjoyable enough to sustain engagement without heavy external scaffolding.

Intrinsic motivation often depends on satisfaction of three psychological needs:

A. Autonomy

• meaningful choices
• self-directed play
• feeling like a causal agent
• not merely obeying prompts

B. Competence

• clear feedback
• felt improvement
• controllable outcomes
• satisfying mastery arc

C. Relatedness

• social connection
• shared play
• mutual recognition
• meaningful belonging

Ask:

• Is the activity fun without the reward wrapper?
• Does the player feel agency while doing it?
• Does the player feel skillful, improving, or effective?
• Does the system support connection or belonging?
• Would engaged players choose this activity even with reduced extrinsic rewards?

Use this format:

Need	Evidence of Satisfaction	Risk of Denial
Autonomy	...	...
Competence	...	...
Relatedness	...	...

8. Map the motivational profile

Summarize the overall mix of motivations the design relies on.

Use this format:

Motivation Type	Strength (Low/Med/High)	Evidence	Design Implication
Amotivation risk	...	...	...
External regulation	...	...	...
Introjected regulation	...	...	...
Identified regulation	...	...	...
Integrated regulation	...	...	...
Intrinsic motivation	...	...	...

Interpretation guidance:

• healthy long-term designs often combine some external regulation for activation, some introjected energy for prestige or momentum, meaningful identified and integrated layers for depth, and strong intrinsic foundations for sustainability
• risky profiles often show high amotivation risk, very high external regulation, weak intrinsic value, and weak deeper internalization

9. Diagnose likely player experience

Translate the profile into likely felt experience.

Example diagnoses:

• reward-chasing but hollow
• socially energizing but intimidating
• compelling for superfans, cold for casuals
• good short-term activation, weak long-term meaning
• strong hobby potential, weak onboarding
• low-agency chore loop
• deeply satisfying mastery loop

Write:

• Likely player experience
• Best-fit audience
• Main retention strength
• Main motivational weakness

10. Recommend motivational adjustments

Recommend changes if the profile is not what the design needs.

Adjustment levers:

To reduce amotivation

• improve context and meaning
• reduce forced or empty taps
• clarify why actions matter
• restore agency and readable outcomes

To reduce overreliance on external regulation

• make the action itself more satisfying
• add autonomy or mastery depth
• reduce pure reward dependency

To tune introjected regulation

• add visible social proof carefully
• add prestige markers without overpunishing the broader audience
• reduce shame or unhealthy comparison pressure where needed

To strengthen identified regulation

• connect actions to larger goals, contribution, purpose, or personally endorsed value

To strengthen integrated regulation

• support specialization, ownership, self-expression, belonging, and long-term mastery communities

To strengthen intrinsic motivation

• improve core feel, choices, skill expression, feedback, and social connection

Write:

• Recommendations

Response structure

Use this structure unless the user asks for something else:

Target Behavior

• ...

Amotivation Risks

• ...

Motivation Breakdown

• External regulation: ...
• Introjected regulation: ...
• Identified regulation: ...
• Integrated regulation: ...
• Intrinsic motivation: ...

Need Satisfaction Check

• Autonomy: ...
• Competence: ...
• Relatedness: ...

Motivational Profile

• ...

Recommendations

• ...

Fast mode

Use this quick pass when speed matters:

• What behavior is this trying to motivate?
• Is the player doing it for the activity, the reward, status, purpose, or identity?
• Where does the design risk feeling empty or forced?
• Which needs does it satisfy: autonomy, competence, relatedness?
• Is this best suited for activation, habit, or deep fandom?

Usage notes

This framework is especially useful for auditing:

• event tracks
• season passes
• city journal or task systems
• leaderboard and club features
• long-term collection systems
• retention surfaces
• monetization loops
• session-opener task flows
• social meta structures

Examples in game design terms:

• External regulation: event rewards, pass milestones, claim loops
• Introjected regulation: rankings, visible rewards, comparative progress
• Identified regulation: club contribution, city stewardship, completion of meaningful builds
• Integrated regulation: collector identity, city stylist identity, deep feature ownership
• Intrinsic motivation: enjoyment of city-building, optimization, planning, and self-expression itself

Working principle

A design is not strong merely because it gets players to act. It is strong when it motivates action in a way that is healthy, satisfying, and sustainable for the intended audience.