CtrlK
BlogDocsLog inGet started
Tessl Logo

anti-cheat-systems

Guide for modern game anti-cheat architecture, Windows kernel monitoring, and detection tradeoffs. Use this skill when analyzing EAC, BattlEye, Vanguard, FACEIT AC, kernel callbacks, handle protection, manual-map detection, boot-start drivers, BYOVD, DMA threats, or behavioral telemetry in game security research.

61

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/anti-cheat/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A rich, well-structured technical reference with clear sequenced workflows and valuable specialized detection content. Its weaknesses are verbosity from inlined reference material, mostly descriptive rather than executable guidance, and broken local file references.

Suggestions

Move the encyclopedic detection-mechanism and ML-classifier sections into separate reference files under references/ and keep SKILL.md as a concise overview that links to them, fixing the broken wiki/ and research-rigor/SKILL.md references.

Delete or trim the 'README Coverage' list and basic explanations (heartbeat, telemetry pipeline, screenshot) that restate concepts Claude already knows, to reduce the ~40KB body toward a lean overview.

Add concrete, executable examples for the highest-value techniques (e.g., a runnable pool-scan or PCIe config-dump snippet) instead of descriptive bullet lists like 'Manual mapping' / 'Thread hijacking'.

DimensionReasoningScore

Conciseness

Mostly specialized content Claude does not reliably know, but padded by the redundant 'README Coverage' list of 40+ category names and basic explanations of heartbeat/telemetry that could be trimmed, matching the 'mostly efficient with some unnecessary explanation' anchor.

3 / 5

Actionability

The Detection Decision Methodology and Data Source fetch instructions are concrete, but large sections (Major Anti-Cheat Systems, Bypass Categories, Code Protection) are descriptive bullet lists ('Manual mapping', 'Thread hijacking') with no executable steps, matching the 'some concrete guidance but incomplete' anchor.

3 / 5

Workflow Clarity

Clear sequenced processes (7-step decision methodology with a 'Review high-impact actions' checkpoint, 6-step DMA layered synthesis, 4-step IOMMU containment) include explicit high-stakes checkpoints, with only minor validation gaps.

4 / 5

Progressive Disclosure

Section structure is present via headers, but encyclopedic content that belongs in separate files is inlined and the only file references (wiki/overviews/anti-cheat.md, ../research-rigor/SKILL.md) point to files that do not exist, matching the 'some structure, content that should be separate is inline' anchor.

3 / 5

Total

13

/

20

Passed

Description

90%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states purpose and triggers with comprehensive, natural keywords and a well-delineated niche. The only weakness is framing capabilities as topics rather than concrete actions.

DimensionReasoningScore

Specificity

Names the domain and several concrete detection areas (manual-map detection, boot-start drivers, BYOVD, DMA threats) but frames them as topics under 'Guide for' rather than as concrete action verbs, matching the score-3 anchor and falling short of the multi-action score-4 example.

3 / 5

Completeness

Explicitly answers both 'what' ('Guide for modern game anti-cheat architecture, Windows kernel monitoring, and detection tradeoffs') and 'when' ('Use this skill when analyzing...') with concrete trigger phrases, matching the score-5 anchor.

5 / 5

Trigger Term Quality

Comprehensive natural terms researchers actually say, including product-name synonyms (EAC, BattlEye, Vanguard, FACEIT AC) plus technical triggers (BYOVD, DMA threats, kernel callbacks), matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (game anti-cheat security research) with distinct product and technique triggers, giving minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (982 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository
gmh5225/awesome-game-security
Reviewed

Table of Contents

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.