# Gsp Audit Scorecard

> Use when converting game audit findings into a structured multi-axis scorecard.

- Skill: `mike007jd/gsp-audit-scorecard-2` (Agent Skill, multi-file: 9 files)
- Install (CLI): `npx skillmds@latest add mike007jd/gsp-audit-scorecard-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mike007jd/gsp-audit-scorecard-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: mike007jd (https://skillmd.com/u/mike007jd)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mike007jd/gsp-audit-scorecard-2

---


# Game Audit Scorecard

## Goal
Normalize audit findings into a structured scorecard that future sessions can read, compare, and build from.

## Outputs

Follow the `gsp-orchestrator` output strategy:
- **inline** (default): present the scorecard and summary in conversation.
- **minimal** or **full**: write to `docs/game-studio/audit/scorecard.json` and `docs/game-studio/audit/audit-summary.md`.

Use:
- `./shared/templates/audit-scorecard.md`
- `./schemas/audit-scorecard.schema.json`
- `./shared/reference/audit-confidence-and-evidence.md`

## Required dimensions
- `ux_flow`
- `hud_readability`
- `feedback_design`
- `audio_feedback`
- `game_feel`
- `mechanics_clarity`
- `scope_completeness`
- `production_readiness`
- `architecture_health`
- `live_risk`

## Important
Scores should be justified by written evidence.
Do not give false precision.
Use consistent severity language and explain uncertainty where runtime evidence is missing.