anti-cheat-systems
Analyze layered anti-cheat architecture, detection evidence, telemetry, and enforcement tradeoffs. Use for system-level defense questions; use narrower skills for DMA, kernel, graphics, mobile, or server details.
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Anti-cheat systems
Map the protected asset, attacker capability, observation point, detector, and enforcement authority. Separate confirmed product behavior from general defensive patterns.
Topic routing
- Architecture and detection for products, client/kernel/backend layers, memory, process, behavior, and input signals.
- Research and threats for analysis methods, bypass categories, platform interactions, protection, telemetry, and ethics.
- Repository map and repository resources for collection-backed source selection.
- Input provenance, detector operations, or network evidence for those specific evidence questions.
Use dma-attack-techniques, windows-kernel-security, graphics-api-hooking, mobile-security, or game-server-security when that boundary dominates. Apply game-security-research-rigor to consequential or disputed claims.
- 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.