Gsp Ux Flow Audit
Use when auditing first-minute onboarding, menus, fail/retry flow, or player comprehension in a game.
Install
$ agentstack add skill-mike007jd-game-superpowers-gsp-ux-flow-audit ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-mike007jd-game-superpowers-gsp-ux-flow-audit) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
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 →About
Game UX Flow Audit
Goal
Audit the player journey and moment-to-moment experience flow, especially the first 30 seconds.
Outputs
Follow the gsp-orchestrator output strategy:
- inline (default): present findings in conversation.
- minimal or full: write to
docs/game-studio/audit/ux-findings.md,docs/game-studio/audit/audit-summary.md,docs/game-studio/audit/scorecard.json.
Use:
./shared/checklists/ux-flow-audit-checklist.md./shared/reference/first-30-seconds.md./shared/reference/audit-confidence-and-evidence.md
Evaluate
- first actionable screen clarity
- onboarding length and interruption cost
- main verb discoverability
- fail / retry / pause / resume flow
- menu-to-play transitions
- whether the UI or setup blocks the core loop
Evidence discipline
Tag each important finding with:
- confidence:
high,medium, orlow - evidence:
code,config,asset,screenshot, orinferred
Output style
Write findings in game-language, such as:
- what the player understands too late
- what the player is asked to do too early
- where friction kills momentum
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: mike007jd
- Source: mike007jd/game-superpowers
- License: MIT
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.