AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Gsp Project Audit

skill-mike007jd-game-superpowers-gsp-project-audit · by mike007jd

Use when running a top-level audit of an existing game project before repair or major changes.

↗ Repository
— No reviews yet
0 installs
25 views
0.0% view→install

Install

$ agentstack add skill-mike007jd-game-superpowers-gsp-project-audit

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-mike007jd-game-superpowers-gsp-project-audit)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Gsp Project Audit? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Game Project Audit

Goal

Audit an existing game project from multiple dimensions before making implementation changes. Default to read-only first.

Default modes

  • audit-only — produce findings only
  • audit-and-plan — produce findings and a repair roadmap
  • audit-and-patch — audit first, then patch only approved high-value issues

Outputs

Follow the gsp-orchestrator output strategy:

  • inline (default): present all findings, scorecard, and repair directions in conversation. Do not create docs/ files.
  • minimal: write only docs/game-studio/audit/audit-summary.md for cross-session reference.
  • full: create and maintain the audit summary, scorecard, UX findings, repair roadmap, and risk register files listed below.

Full output files (when strategy = full):

  • docs/game-studio/audit/audit-summary.md
  • docs/game-studio/audit/scorecard.json
  • docs/game-studio/audit/ux-findings.md
  • docs/game-studio/audit/repair-roadmap.md
  • docs/game-studio/audit/risk-register.md

Use:

  • ./shared/templates/audit-summary.md
  • ./shared/templates/audit-scorecard.md
  • ./shared/templates/ux-findings.md
  • ./shared/templates/repair-roadmap.md
  • ./shared/templates/risk-register.md
  • ./shared/checklists/project-audit-master-checklist.md
  • ./shared/checklists/ui-ux-hard-rules.md
  • ./shared/reference/audit-modes.md
  • ./shared/reference/audit-confidence-and-evidence.md

Audit workflow

  1. Assess project state and release risk with gsp-project-state-assessment.
  2. Determine audit mode and focus dimensions.
  3. Run the relevant sub-audits:
  • gsp-ux-flow-audit
  • gsp-hud-readability-audit
  • gsp-feedback-audit
  • gsp-audio-feedback-audit
  • gsp-feel-audit
  • gsp-mechanics-systems-audit
  • gsp-scope-completeness-audit
  • gsp-production-readiness-audit
  • gsp-architecture-maintainability-audit
  • gsp-live-risk-audit when the repo is shipped or high-risk
  1. Consolidate findings with gsp-audit-scorecard.
  2. If requested, create a prioritized fix plan with gsp-repair-roadmap.
  3. Patch only after the audit report exists and the requested mode allows edits.

Rules

  • Never start by changing files when the request is clearly an audit.
  • Distinguish between confirmed issues and high-confidence inferred issues.
  • Always include evidence and confidence for important findings.
  • Prefer game-native language over frontend jargon.
  • Call out hard-rule violations when UI flow, HUD pressure, or input-focus conflicts are likely hurting the player experience.

Stop condition

You are done when the project has a clear audit summary, a dimensional scorecard, a risk register, and a repair roadmap if requested.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills