CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

An exemplary overview/router skill: near-zero token waste, clearly signaled one-level references that all resolve to real files, and explicit cross-skill boundaries. The only headroom is a lack of worked examples for the opening mapping instruction and implicit rather than explicit step ordering.

DimensionReasoningScore

Conciseness

The ~18-line body is lean and efficient: a one-sentence framing directive ("Map the protected asset, attacker capability, observation point, detector, and enforcement authority"), a compact routing list, and one delegation line. Nothing explains concepts Claude already knows and every token earns its place.

5 / 5

Actionability

Concrete guidance is present: a specific opening analytical instruction, per-file routing that states what each reference covers (e.g., "[Research and threats](references/research-and-threats.md) for analysis methods, bypass categories..."), and conditional cross-skill delegation ("Apply `game-security-research-rigor` to consequential or disputed claims"). It stops short of the 5 anchor because no worked example shows how to execute the mapping instruction.

4 / 5

Workflow Clarity

An implicit sequence is legible: map the five concepts, route to the matching reference, escalate disputed claims to the rigor skill. For a router-style skill the single action is unambiguous, but the ordering is implicit rather than an explicit numbered sequence, matching anchor 4 rather than 5. No destructive or batch operations, so no validation cap applies.

4 / 5

Progressive Disclosure

This is the canonical router pattern: a concise overview with well-signaled one-level-deep references, each annotated with the topics it covers, and all 7 referenced files verified present in references/. Content is appropriately split out of SKILL.md, matching the clear-overview anchor exemplar.

5 / 5

Total

18

/

20

Passed

Description

78%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 with an explicit trigger clause, concrete domain-specific objects of analysis, and unusually good boundary demarcation against sibling skills. Slight headroom remains in trigger-phrase concreteness and natural-synonym coverage.

DimensionReasoningScore

Specificity

"Analyze layered anti-cheat architecture, detection evidence, telemetry, and enforcement tradeoffs" names the domain plus several concrete objects of analysis, but rests on a single verb, leaving minor gaps versus the multi-action anchor at 5. Not 3 because coverage extends well beyond 1-2 actions.

4 / 5

Completeness

Both parts are present: the "what" ("Analyze layered anti-cheat architecture, detection evidence, telemetry, and enforcement tradeoffs") and an explicit "when" ("Use for system-level defense questions"). The trigger clause is present and explicit, but "system-level defense questions" is more abstract than concrete trigger phrases like "when the user mentions X", matching the anchor 4 rather than 5.

4 / 5

Trigger Term Quality

Natural terms include "anti-cheat", "detection evidence", "telemetry", "enforcement", plus boundary terms "DMA", "kernel", "graphics", "mobile", "server". Common user synonyms like "cheating", "game hacking", "bans", or named products (EAC, BattlEye) are missing, so it falls just short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

It carves a clear system-level niche and actively disambiguates with "use narrower skills for DMA, kernel, graphics, mobile, or server details", which minimizes wrong-skill triggering. This matches the clear-niche anchor with minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

gmh5225/awesome-game-security

Path

.claude/skills/anti-cheat/SKILL.md

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.