game-design-one-thing-to-remove — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited game-design-one-thing-to-remove (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Improve the design by cutting one thing, not by adding three more.
Use this skill when a design would likely become better through subtraction. The goal is not to nitpick random dislikes. The goal is to identify the one removal with the highest leverage: the thing whose absence would most improve clarity, pacing, focus, emotional impact, usability, production efficiency, or strategic coherence.
Read references/removal-lenses.md when deciding what kind of thing is most worth cutting. Read references/evaluation-patterns.md when you need the exact output pattern.
Produce:
Clarify:
Check whether the design contains:
Pick one thing only. Do not list five cuts unless the user explicitly asks. Choose the removal whose absence would improve the design most significantly.
Good candidates include:
Do not say only that the design becomes “cleaner.” Explain exactly what improves, such as:
A good cut may still remove something useful. State what is lost and whether that loss matters. If appropriate, suggest a lighter substitute that preserves the upside without keeping the full problematic element.
End with a decision such as:
Many designs get worse because every problem is answered with addition. Sometimes the best improvement is subtraction with intent.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.