Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeDeclared
CursorNot declared
CodexDeclared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars1
LicenseLICENSE
Default branchmain
Open issues0
Status
Active
Skill metadata
Parsed from SKILL.md frontmatter.
Version0.1.0
LicenseMIT
CompatibilityCodex, Claude Code, and other Agent Skills-compatible clients.
Declared agentsclaude-codecodex
More metadata
version
0.1.0
displayName
Game Responsibility Review
category
Game Development
tags
game-design,ethics,safety,monetization,community
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md2,190 B
docsSUMMARY.md316 B
History
First seen on skills.sh
First recorded snapshot · 55 installs
SKILL.md
Game Responsibility Review
Use this skill to evaluate what a game teaches, rewards, pressures, or normalizes. The goal is not to remove all friction or intensity; it is to make deliberate choices about player impact.
Source Traceability
Primary source: The Art of Game Design: A Book of Lenses, Third Edition by Jesse Schell, especially chapters 33-35 on transformation, responsibility, and purpose. The workflow is transformed and paraphrased.
Supporting sources include accessibility guidance and community safety practice where relevant.
Workflow
State the intended player transformation or after-effect.
Identify pressures created by rewards, scarcity, social comparison, streaks, ads, monetization, and notifications.
Review vulnerable player contexts: children, compulsive behavior, spending pressure, harassment, exclusion, and accessibility barriers.
Distinguish deliberate tension from accidental harm.
Recommend design changes, policy limits, instrumentation, and review gates.
Required Output
Purpose Statement: what the game should leave players with.
Impact Map: beneficial, neutral, and risky effects.
Pressure Review: retention, monetization, social, scarcity, and notification mechanics.
Risk Controls: product changes, limits, disclosures, parental or accessibility options, moderation, and telemetry.
Ship Gate: unresolved issues that should block release or require explicit owner approval.