reverse-engineering-tools

Investigate supplied game binaries, protection components, drivers, dumps, and traces through reproducible binary analysis. Use for repository resource selection, PE/symbol inspection, disassembly and decompilation, control/data-flow reconstruction, build comparison, obfuscation classification, and interface evidence with IDA, Ghidra or debuggers. Match tool scope to the artifact and produce versioned findings with addresses, provenance, uncertainty and defensive implications.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

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

The body is well-structured and rich in domain coverage with a properly used reference file, but it is verbose, leans on descriptive catalogs over executable guidance, and inlines material that would benefit from being split into references.

Suggestions

Move the large tool/plugin catalogs (Disassembler Plugin Ecosystem, Anti-Debug Techniques Catalog, Obfuscation Taxonomy) into separate reference files and keep SKILL.md as an overview with one-level links, mirroring the existing repository-resources.md pattern.

Tighten or remove enumerative tool listings that simply restate well-known tools (e.g. "IDA Pro: Industry standard disassembler") to reduce token cost without losing guidance value.

Add explicit validation checkpoints to the analysis workflows (e.g. a verify step after structure recovery or build diffing) so the rigor guidance becomes concrete workflow steps rather than prose.

Dimension	Reasoning	Score
Conciseness	Mostly specialized content but padded with long enumerative catalogs (debugger lists, plugin ecosystems, anti-debug entries) that could be tightened; it is not a 2 because it avoids explaining basic concepts Claude already knows and includes valuable rigor guidance.	3 / 5
Actionability	The repository Data Source section gives concrete paths and raw URLs, but the RE-technique sections are descriptive taxonomy with little executable code or specific commands, leaving the guidance incomplete rather than fully actionable.	3 / 5
Workflow Clarity	Numbered analysis sequences exist (Initial/Deep Analysis, game-specific steps) and rigor prose stresses validation, but checkpoints are implicit rather than explicit workflow steps, so it sits at the listed-but-gaps level rather than the clear-checkpoint level of a 4.	3 / 5
Progressive Disclosure	A real one-level reference (references/repository-resources.md, verified present) is clearly signaled twice, but substantial catalog content (plugin ecosystems, obfuscation taxonomy, anti-debug catalog) is inlined in SKILL.md that could be split into separate files.	3 / 5
	Total	12 / 20 Passed

Description

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

The description is specific, complete, and clearly distinct, with an explicit "Use for" trigger clause and concrete actions tied to named tools. Its only gap is missing synonyms/file extensions that would make the trigger-term coverage fully comprehensive.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the domain — "PE/symbol inspection, disassembly and decompilation, control/data-flow reconstruction, build comparison, obfuscation classification, and interface evidence with IDA, Ghidra or debuggers" — giving comprehensive coverage rather than the minor-gaps level of a 4.	5 / 5
Completeness	Clearly states what ("Investigate supplied game binaries... through reproducible binary analysis") and explicitly when via the "Use for repository resource selection, PE/symbol inspection..." trigger clause, with concrete trigger phrases and third-person voice.	5 / 5
Trigger Term Quality	Strong natural terms ("game binaries", "IDA, Ghidra or debuggers", "disassembly and decompilation", "dumps, traces") but it omits file extensions and the phrase "reverse engineering" itself, so it does not reach the comprehensive-with-synonyms/extensions level of a 5.	4 / 5
Distinctiveness Conflict Risk	A clear niche — game binaries, protection components, drivers, dumps, traces with named tooling — yields distinct triggers and minimal conflict risk with unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (527 lines); consider splitting into references/ and linking	Warning
relative_links	Relative link issues: 11 suspicious	Warning

	Total	14 / 16 Passed

Repository: gmh5225/awesome-game-security
Path: .claude/skills/reverse-engineering/SKILL.md
Commit: c7e4d3f

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.