Skill: mike007jd/game-audit-scorecard (version 1.0.0)

--- name: game-audit-scorecard description: Summarize audit findings into a structured multi-dimensional scorecard for UI/UX, feedback, mechanics, scope completeness, maintainability, and live risk. license: MIT compatibility: Claude Code and Codex. Best results with file read/write access; shell/build access improves evidence quality. metadata: author: game-superpowers version: "1.1.0" domain: game-development --- # Game Audit Scorecard ## Goal Normalize audit findings into a structured scorecard that future sessions can read, compare, and build from. ## Deliverables Create or update: - `docs/game-studio/audit/scorecard.json` - `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.

path: CHANGELOG.md
content: # Changelog

## 1.1.0 — 2026-03-30

- Initial ClawHub publish bundle generated from `skills/game-audit-scorecard/SKILL.md`.
- Added bundle metadata, README, and MANIFEST for OpenClaw / ClawHub distribution.


path: MANIFEST.yaml
content: bundle: game-audit-scorecard
bundle_version: 1.1.0
bundle_date: 2026-03-30
description: >
  Summarize audit findings into a structured multi-dimensional scorecard for UI/UX, feedback, mechanics, scope completeness, maintainability, and live risk.
compatibility:
  designed_for:
    surfaces:
      - chat
      - cli
      - ide
    capabilities:
      - local filesystem access
      - markdown skill bundles
      - reusable game-development workflows
  tested_on:
    - platform: OpenClaw
      surface: ClawHub
      status: pending
      date: 2026-03-30
    - platform: Claude Code
      surface: CLI
      status: pass
      date: 2026-03-30
    - platform: Codex
      surface: CLI
      status: pass
      date: 2026-03-30
  spec_version: agentskills.io/1.0
  frontmatter_mode: metadata
dependencies:
  []
files:
  - path: CHANGELOG.md
    role: reference
    version: 1
    hash: sha256:656b731d76020cd38bab31c98b98dbb22f77b7acb5474d99720fabb10ae05611
    note: Bundle release notes
  - path: README.md
    role: reference
    version: 1
    hash: sha256:a06f749bc3d6a3500e82edcaf4912fd43afb57f944442de2283924a83f591d6f
    note: ClawHub-facing usage and context
  - path: SKILL.md
    role: skill
    version: 1
    hash: sha256:18c0df552c1c2972833862287e2d0e24d00dc6c167e133119e2b2141a6b4dabf
    note: Canonical skill definition for this publish bundle
  - path: examples/usage.md
    role: reference
    version: 1
    hash: sha256:904d8a66f009acc4fc96c9daffc2c891871d269779ff959aaf66bc288357bf83
    note: Referenced support file: examples/usage.md
  - path: schemas/audit-scorecard.schema.json
    role: reference
    version: 1
    hash: sha256:df9818a11e3bab3f737568d132f5db3e818a3f6e7342198a5f506189442fa529
    note: Referenced support file: schemas/audit-scorecard.schema.json
  - path: shared/reference/audit-confidence-and-evidence.md
    role: reference
    version: 1
    hash: sha256:befa83a5f1c08e9cb3a2596007d3b6d7d1ab2c8e57b7d929db2e514187a0d16d
    note: Referenced support file: shared/reference/audit-confidence-and-evidence.md
  - path: shared/templates/audit-scorecard.md
    role: reference
    version: 1
    hash: sha256:3db43f487dcc5ac71ca5a2d06fd422963c151301e1f203dc1c4bb4ba9c010e73
    note: Referenced support file: shared/templates/audit-scorecard.md
  - path: tests/smoke.md
    role: reference
    version: 1
    hash: sha256:621feeba353b7299aa908852a66b4d5b7bee19d20b0212cc6a446932f48ea748
    note: Referenced support file: tests/smoke.md


path: README.md
content: # game-audit-scorecard

Part of the **Game Superpowers** skill system.

## Summary

Summarize audit findings into a structured multi-dimensional scorecard for UI/UX, feedback, mechanics, scope completeness, maintainability, and live risk.

## Recommended usage

- Use `game-audit-scorecard` for this game project and keep the output evidence-based.
- Apply `game-audit-scorecard` to improve or assess an existing browser game in a focused way.
- Use `game-audit-scorecard` as part of a larger Game Superpowers workflow when the request clearly matches game audit scorecard.

## Companion skills

- None

## Source of truth

This publish bundle is derived from the Game Superpowers source repository.
Canonical authoring lives in:

```text
skills/game-audit-scorecard/SKILL.md
```

## Notes

- This bundle is published for OpenClaw / ClawHub distribution.
- The Game Superpowers repository also supports Claude Code and Codex distributions.
- If a workflow references companion skills, install those companion skills as separate bundles.


path: examples/usage.md
content: # Usage Examples

## Example prompts

- Use `game-audit-scorecard` for this game project and keep the output evidence-based.
- Apply `game-audit-scorecard` to improve or assess an existing browser game in a focused way.
- Use `game-audit-scorecard` as part of a larger Game Superpowers workflow when the request clearly matches game audit scorecard.

## Expected behavior

- Load the skill instructions from `SKILL.md`.
- Use any packaged `shared/` references when the skill body points to them.
- If the workflow calls for companion skills, tell the user which companion skills should be installed or invoked next.


path: schemas/audit-scorecard.schema.json
content: {
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "Game Superpowers Audit Scorecard",
  "type": "object",
  "required": [
    "project_state",
    "audit_mode",
    "dimensions"
  ],
  "properties": {
    "project_state": {"type": "string"},
    "audit_mode": {
      "type": "string",
      "enum": ["audit-only", "audit-and-plan", "audit-and-patch"]
    },
    "dimensions": {
      "type": "object",
      "required": [
        "ux_flow",
        "hud_readability",
        "feedback_design",
        "audio_feedback",
        "game_feel",
        "mechanics_clarity",
        "scope_completeness",
        "production_readiness",
        "architecture_health",
        "live_risk"
      ],
      "properties": {
        "ux_flow": {"type": "number", "minimum": 0, "maximum": 10},
        "hud_readability": {"type": "number", "minimum": 0, "maximum": 10},
        "feedback_design": {"type": "number", "minimum": 0, "maximum": 10},
        "audio_feedback": {"type": "number", "minimum": 0, "maximum": 10},
        "game_feel": {"type": "number", "minimum": 0, "maximum": 10},
        "mechanics_clarity": {"type": "number", "minimum": 0, "maximum": 10},
        "scope_completeness": {"type": "number", "minimum": 0, "maximum": 10},
        "production_readiness": {"type": "number", "minimum": 0, "maximum": 10},
        "architecture_health": {"type": "number", "minimum": 0, "maximum": 10},
        "live_risk": {"type": "number", "minimum": 0, "maximum": 10}
      }
    },
    "top_issues": {"type": "array", "items": {"type": "string"}},
    "quick_wins": {"type": "array", "items": {"type": "string"}},
    "high_risk_areas": {"type": "array", "items": {"type": "string"}},
    "confidence_notes": {"type": "array", "items": {"type": "string"}},
    "evidence_summary": {
      "type": "object",
      "properties": {
        "confirmed_findings": {"type": "integer", "minimum": 0},
        "inferred_findings": {"type": "integer", "minimum": 0},
        "missing_runtime_evidence": {"type": "array", "items": {"type": "string"}}
      }
    }
  }
}


path: shared/reference/audit-confidence-and-evidence.md
content: # Audit Confidence and Evidence

Every important finding should include:
- `confidence`: `high`, `medium`, or `low`
- `evidence`: one or more of `code`, `config`, `asset`, `screenshot`, `docs`, `inferred`

Use `high` when the issue is directly supported by implementation evidence.
Use `medium` when several signals point the same way but runtime proof is missing.
Use `low` when the issue is plausible but weakly evidenced.

Prefer explicit uncertainty over false confidence.


path: shared/templates/audit-scorecard.md
content: # Audit Scorecard Shape

Write `docs/game-studio/audit/scorecard.json` using the audit scorecard schema.
Include:
- project state
- audit mode
- dimensions
- top issues
- quick wins
- high risk areas
- confidence notes
- evidence summary


path: tests/smoke.md
content: # Smoke Test

Bundle: `game-audit-scorecard`
Version: `1.1.0`

## Prompt

Use `game-audit-scorecard` on a fitting game-development task.

## Expected checks

- The agent recognizes the skill's stated purpose.
- The agent uses packaged references when `SKILL.md` points to `./shared/...`.
- The agent does not claim companion skills are bundled implicitly when they are separate installs.
- Companion skills referenced in this bundle: none


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)