CtrlK
BlogDocsLog inGet started
Tessl Logo

reverse-engineering-tools

Guide for reverse engineering protected games and anti-cheat components across user mode, kernel mode, and hypervisor-aware environments. Use this skill when analyzing drivers, IOCTL protocols, callback registration, injected-code artifacts, integrity checks, protected binaries, or debugging security-sensitive game components.

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/reverse-engineering/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The body is a broad, well-organized reference catalog with genuine domain depth, but it is verbose, lacks executable examples, and keeps content inline rather than splitting it across bundle files. It lands at the middle band across conciseness, actionability, workflow clarity, and progressive disclosure.

Suggestions

Move the long tool/plugin catalogs into bundled reference files (e.g., references/tools.md, references/plugins.md) and keep SKILL.md as a lean overview that links one level deep, improving both conciseness and progressive_disclosure.

Add at least one executable snippet or concrete command sequence (e.g., a Frida hook template or an archive-fetch command) to lift actionability from descriptive to copy-paste ready.

Add explicit validation/checkpoint steps to the analysis workflows — e.g., confirm protections identified before deep tracing, or verify an archive fetch succeeded before relying on it — to raise workflow_clarity.

DimensionReasoningScore

Conciseness

The ~500-line body is a large catalog enumerating dozens of tools and technique summaries; while much is domain-specific value-add Claude lacks, the sheer volume of list-style reference content could be tightened or offloaded, matching the "mostly efficient but could be tightened" anchor rather than the lean 3.

2 / 3

Actionability

It names tools and describes techniques concretely (sentinel opcodes, API names, URL formats) but provides almost no executable code or copy-paste commands; as an instruction/catalog skill the guidance is actionable in places yet incomplete, fitting the 2 anchor.

2 / 3

Workflow Clarity

Numbered workflows exist (Initial/Deep Analysis, game-specific steps, archive/description fetch with priority order and 404 fallback), but validation checkpoints and feedback loops are absent, capping it at 2 per the anchor.

2 / 3

Progressive Disclosure

Section structure and external/wiki references are signaled, but no bundle files exist and the catalog content is largely inline in a monolithic body that could be split into reference files, matching the 2 rather than the well-split 3.

2 / 3

Total

8

/

12

Passed

Description

100%

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

The description is specific, complete, and well-targeted: it states concrete capabilities and gives an explicit "Use this skill when..." trigger clause covering the domain's natural vocabulary. No weakness warrants a reduction on any dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "analyzing drivers, IOCTL protocols, callback registration, injected-code artifacts, integrity checks, protected binaries, or debugging security-sensitive game components" — matching the anchor for enumerating specific actions.

3 / 3

Completeness

Explicitly answers both "what" ("Guide for reverse engineering protected games and anti-cheat components across user mode, kernel mode, and hypervisor-aware environments") and "when" ("Use this skill when analyzing drivers, IOCTL protocols...").

3 / 3

Trigger Term Quality

Covers natural domain terms a user would say (drivers, IOCTL, callbacks, injected code, integrity checks, protected binaries, debugging) with good breadth; not reduced because these are the genuine vocabulary for this niche.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche — game anti-cheat RE across user/kernel/hypervisor layers — with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

Total

15

/

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.