game-security-research-rigor

Validates game-security claims through citation verification, claim ledgers, and detector evaluation.

3.5k|488|Updated Apr 4, 2022
One-click install
npx skills add https://github.com/gmh5225/awesome-game-security --skill game-security-research-rigor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: game-security-research-rigor
Source: https://github.com/gmh5225/awesome-game-security/tree/main/.claude/skills/research-rigor
Command: npx skills add https://github.com/gmh5225/awesome-game-security --skill game-security-research-rigor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Game-security research often mixes raw observations with unverified attribution, leading to overstated anti-cheat conclusions, uncalibrated detectors, and citations that do not actually support the claims made. This Skill enforces evidence-grounded reasoning so conclusions never exceed what the data supports.

Core Features & Use Cases

  • Layered Reasoning Discipline: Separates observation, finding, attribution, and decision so an anomaly or invariant violation is never automatically treated as proof of cheating.
  • Citation Verification & Claim Ledger: Verifies every URL, DOI, and source against authoritative metadata, then records each claim with its evidence, assumptions, counterevidence, and uncertainty label.
  • Detector & Telemetry Evaluation: Guides calibration of anti-cheat detectors with proper data splitting, confusion matrices, prevalence reporting, and revalidation after patches or population drift.
  • Use Case: When comparing two anti-cheat techniques described across README files and vendor posts, use this Skill to verify each source, label claims as observed or inferred, and conclude narrowly (supported, suspicious, or inconclusive) instead of overstating the evidence.

Quick Start

Ask the AI to evaluate whether the evidence in these game-security sources supports the claim that a specific anti-cheat technique detects DMA cheats, and to produce a claim ledger with verified citations.

Frequently Asked Questions about game-security-research-rigor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify citations in game security research?

Verify citations by confirming the URL or DOI resolves, matching title, authors, venue, and year against authoritative metadata, and reading enough of the source to confirm it supports the exact claim. A venue name or search result alone is not evidence.

How to evaluate an anti-cheat detector without false positives?

Evaluate anti-cheat detectors by splitting data by player and session, including legitimate and accessibility-tool users, and reporting a confusion matrix with false-positive rate, recall, and calibration. Revalidate thresholds after patches, balance changes, and population drift.

What is the difference between an observation and attribution in cheat detection?

An observation is the raw artifact or measurement, while attribution is a hypothesis about cause or actor intent. An anomaly or invariant violation establishes a finding only under stated measurement assumptions and does not by itself prove cheating or malicious intent.

Does an invariant violation prove a player is cheating?

No, an invariant violation does not prove cheating by itself. First confirm the invariant is guaranteed for that build, exclude replication delay, rollbacks, reconnects, and game bugs, and distinguish state-integrity violations from attribution of exploitation.

When should a game security conclusion be marked inconclusive?

Mark a conclusion inconclusive when quality gates fail, such as unverified citations, untested benign alternatives, or missing representative evaluation data. Never fabricate sources or raise confidence to fill gaps; narrow the claim instead.