game-security-research-rigor
Verify consequential or disputed game-security claims with primary sources, reproducible evidence, explicit trust boundaries, and calibrated uncertainty. Use alongside a domain skill when evidence quality affects the conclusion.
Game security research rigor
Keep conclusions no stronger than the evidence. Separate observation, finding, attribution, and action, and record temporal and environmental limits.
Topic routing
- Claims and workflow for reasoning layers, research steps, and versioned claim records.
- Evaluation and governance for detector metrics, invariants, decision policy, quality gates, and test limits.
- Sources and repository evidence for source roles and collection-specific evidence.
- Robustness and triage for confounders, adversarial inputs, and disagreement.
- Skill evaluation for catalog routing tests.
State what would falsify the conclusion and what evidence remains unavailable. Do not convert a repository summary, community report, or absence of evidence into a verified product claim.
- Repository
gmh5225/awesome-game-security
- Revision
b439093
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.