Install
$ agentstack add skill-mike007jd-game-superpowers-gsp-scope-guard ✓ 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.
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 Scope Guard
Goal
Keep scope under control while preserving the value of the request.
Core rule
Do not equate “scope control” with “remove everything interesting.”
By mode
- yolo-super / guided-build: protect the user’s core requested feature set. Cut edge cases, not the fantasy.
- refactor-open: protect the outcome, but allow larger architecture change when it prevents endless patching.
- surgical-live: minimize blast radius first; here scope control often means tighter change boundaries.
Good cuts
- optional content multiplication
- edge-case polish outside the critical path
- tooling not needed for the current target
- deep progression systems when the target does not require them
Bad cuts
- requested core mechanic
- requested style / feel / UX quality if that is central to the ask
- essential fail/retry and onboarding clarity
- architecture cleanup that is necessary to make the requested change stable
Outputs
Follow the gsp-orchestrator output strategy:
- inline (default): state scope decisions and rationale in conversation.
- minimal or full: record the rationale in
docs/game-studio/plan.mdordocs/game-studio/build-strategy.md.
Pair with
Use gsp-scope-profile early to define the intended scope. This skill protects it later.
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.