Gsp Screenshot Critic
Use when critiquing screenshots or visual captures for readability, hierarchy, and target-quality fit.
Install
$ agentstack add skill-mike007jd-game-superpowers-gsp-screenshot-critic ✓ 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-screenshot-critic) 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 Screenshot Critic
Goal
Use visual evidence to judge whether the build actually looks understandable and good enough for the target.
Use
./shared/checklists/screenshot-critic-output-checklist.md./shared/checklists/ui-ux-hard-rules.md
Focus
- information hierarchy
- clutter
- readability
- playfield protection
- visual coherence
- perceived completeness
- whether feedback cues are visible
- whether persistent HUD feels disciplined or bloated
By target
- first-playable: look for basic readability and affordance
- polished-prototype: hold a higher bar for coherence and perceived finish
- production-feature / live-patch: check consistency with the rest of the product
Outputs
Follow the gsp-orchestrator output strategy:
- inline (default): present critique findings and repair priorities in conversation.
- minimal or full: append to
docs/game-studio/quality-report.md.
Reporting rules
Separate:
- confirmed strengths
- confirmed issues
- inferred risks
- repair priorities
Important
Do not overstate what a screenshot proves. Use screenshots to strengthen evidence, not to hallucinate certainty.
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.