rev-u3d-dump

Dump Unity IL2CPP symbols from iOS/Android builds. Extract method names, addresses, and type info from IL2CPP binaries and global-metadata.dat, then generate IDA/Ghidra import scripts.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%

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

A highly actionable, concise procedural skill with a clear sequenced workflow and built-in validation checkpoints. The main weakness is the absence of any progressive disclosure via separate reference files despite a moderately long body.

Suggestions

Split the Troubleshooting table and Tool Selection comparison into a separate reference file (e.g. TROUBLESHOOTING.md) referenced from the body, to shorten the main SKILL.md and add a one-level-deep reference.

Move the IDA/Ghidra import step details and output-usage tips into a referenced ADVANCED.md, keeping SKILL.md as a lean overview with a quick-start path.

Dimension	Reasoning	Score
Conciseness	The body is lean: dense bash/git/dotnet commands, tables, and JSON examples with only a single sentence of problem framing; it assumes Claude's competence and avoids generic concept padding. It is not a 2 because no explanatory filler or verbosity is present.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands (unzip, xxd, git clone, dotnet build/run) with concrete paths, plus exact output formats. It is not a 2 because nothing is pseudocode or abstract.	3 / 3
Workflow Clarity	Sequenced Steps 1–5 with explicit validation checkpoints (metadata version check in Step 2, output verification in Step 4) and an error-recovery troubleshooting table. It is not a 2 because validation and feedback loops are present and explicit.	3 / 3
Progressive Disclosure	Sections are well-organized, but the skill is a monolithic ~170-line single file with no bundle references or content split, exceeding the under-50-line simple-skill exception that would allow a 3. It is not a 1 because navigation via clear section headings is good and references are not nested.	2 / 3
	Total	11 / 12 Passed

Description

82%

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 specific, well-targeted description with concrete actions and natural domain terms, written in correct third-person voice. Its only gap is the absence of an explicit 'Use when...' trigger clause.

Suggestions

Add an explicit trigger clause, e.g. 'Use when reverse-engineering Unity IL2CPP iOS/Android builds to recover C# symbol names for IDA/Ghidra.'

Include common user phrasings such as 'Unity game', 'IL2CPP dumper', or 'recover method names' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Dump Unity IL2CPP symbols', 'Extract method names, addresses, and type info', and 'generate IDA/Ghidra import scripts' — each tied to specific artifacts (IL2CPP binaries, global-metadata.dat).	3 / 3
Completeness	Clearly states what the skill does, but lacks any 'Use when...' clause or equivalent explicit trigger guidance; per the rubric this caps completeness at 2. It is not a 1 because the 'what' is comprehensive and concrete.	2 / 3
Trigger Term Quality	Uses natural domain terms a reverse-engineering user would actually say — 'Unity', 'IL2CPP', 'global-metadata.dat', 'IDA/Ghidra', 'iOS/Android builds' — with good coverage of the niche vocabulary.	3 / 3
Distinctiveness Conflict Risk	The niche is sharply defined (Unity IL2CPP symbol recovery for IDA/Ghidra on iOS/Android) and would not reasonably trigger for unrelated skills. It is not below 3 because no overlap with generic skills exists.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing, 1 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: P4nda0s/reverse-skills
Path: skills/rev-u3d-dump/SKILL.md
Commit: a2baa31

Reviewed: about 1 hour 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.