CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reverse-engineer

Expert reverse engineer specializing in binary analysis, disassembly, decompilation, and software analysis. Masters IDA Pro, Ghidra, radare2, x64dbg, and modern RE toolchains. Handles executable analysis, library inspection, protocol extraction, and vulnerability research. Use for binary analysis, CTF challenges, security research, or understanding undocumented software.

Quality

71%

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

Fix and improve this skill with Tessl

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

Quality

Content

42%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 has a sensible four-phase methodology and genuinely useful concrete examples (commands, anti-debug/API-hashing patterns), but it is dragged down by template filler sections — one referencing a mismatched domain — textbook-knowledge recitation, and no progressive disclosure of reference material. The main workflow also lacks executable specifics and validation checkpoints.

Suggestions

Delete the content-free filler sections ('Use this skill when', 'Do not use this skill when', 'Instructions', 'Response Approach') — the use/do-not-use sections reference 'common re scripting environments', which doesn't even match this skill's domain — and cut the calling-conventions list, which restates knowledge Claude already has.

Make the Analysis Methodology phases executable: add concrete tool invocations per phase (e.g., specific radare2/Ghidra-headless commands for static analysis, Frida scripts or gdb command sequences for dynamic analysis) instead of directional phrases like 'Load into disassembler: Configure analysis options appropriately'.

Add explicit validation checkpoints linking the phases (e.g., 'confirm static-analysis hypotheses by setting breakpoints on the identified functions before documenting') so the methodology has feedback loops rather than a one-way sequence.

DimensionReasoningScore

Conciseness

Several sections are pure padding: 'Use this skill when' / 'Do not use this skill when' are template boilerplate that even references the wrong domain ('common re scripting environments'), 'Instructions' is content-free ('Apply relevant best practices and validate outcomes'), 'Response Approach' is generic, and the calling-conventions list restates textbook knowledge Claude already knows. This matches 'noticeably verbose; several unnecessary explanations or padded sections' — the lean methodology and pattern sections keep it above the 'severely verbose' anchor.

2 / 5

Actionability

The Example Interactions include real executable commands ('file challenge', 'checksec --file=challenge', 'gdb ./challenge', 'dumpbin /exports') and the code-pattern snippets are concrete C. However, the core Analysis Methodology — the skill's main guidance — stays directional ('Load into disassembler: Configure analysis options appropriately', 'Isolated VM, network monitoring, API hooks') without specific commands or tool invocations, fitting 'some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

The four-phase methodology (Reconnaissance → Static → Dynamic → Documentation) is clearly sequenced with numbered steps, and the CTF example has a mini feedback loop (breakpoint → run → examine memory). But the methodology itself has no explicit validation checkpoints — hypotheses from static analysis are never verified against dynamic results — matching 'steps listed but validation gaps; checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

Section headers are clear and logically ordered, so structure is present, but roughly half the body (~80 lines of code patterns, calling conventions, and worked examples) is reference material inlined directly in SKILL.md with no external files at all. This fits 'some structure but could be better organized; content that should be separate is inline' — and at ~160 lines the under-50-line simple-skill exception does not apply.

3 / 5

Total

11

/

20

Passed

Description

88%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 capabilities in third person and includes an explicit 'Use for' trigger clause with concrete scenarios. Its only weaknesses are slightly padded persona phrasing ('Masters...') and trigger terms broad enough ('security research') to overlap with adjacent security skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'binary analysis, disassembly, decompilation', 'executable analysis, library inspection, protocol extraction, and vulnerability research' — which comprehensively cover the reverse-engineering domain. Minor vague padding ('software analysis', 'Masters... modern RE toolchains') exists but does not create coverage gaps, so this fits the 'comprehensive coverage' anchor rather than the 'minor gaps' anchor below it.

5 / 5

Completeness

Both questions are explicitly answered: the 'what' via 'Handles executable analysis, library inspection, protocol extraction, and vulnerability research', and the 'when' via an explicit 'Use for...' clause with four concrete trigger phrases. The trigger guidance is equivalent to a 'Use when...' clause, so the missing-trigger cap does not apply, and the 'when' is specific enough to exceed the 'could be more explicit' anchor.

5 / 5

Trigger Term Quality

The 'Use for binary analysis, CTF challenges, security research, or understanding undocumented software' clause plus capability nouns like 'disassembly' and 'decompilation' give good natural keyword coverage. Common variations users would say — 'malware analysis', 'decompile this binary', and file extensions like .exe/.dll/.elf — are missing, so it does not reach the comprehensive-synonyms-and-extensions anchor.

4 / 5

Distinctiveness Conflict Risk

The binary-analysis/CTF/disassembly niche is clear and distinct from most skills, matching 'clear niche'. However, the broad triggers 'security research' and 'vulnerability research' could also plausibly match a general security or pentesting skill, which is minor overlap with closely related skills rather than minimal conflict risk.

4 / 5

Total

18

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

skills/reverse-engineer/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.