binary-analysis-patterns

Comprehensive patterns and techniques for analyzing compiled binaries, understanding assembly code, and reconstructing program logic.

Quality

53%

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 ./skills/binary-analysis-patterns/SKILL.md

Quality

Content

53%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 skill is rich with concrete, executable assembly and tool-scripting examples, but it reads as a monolithic textbook dump of patterns Claude largely already knows, padded with generic boilerplate, and its single progressive-disclosure pointer is a broken reference. Splitting the reference material into real bundle files and trimming the boilerplate would meaningfully improve it.

Suggestions

Move the Ghidra and IDA Pro scripting sections (and optionally the assembly pattern catalog) into separate reference files under references/, and link to them from a concise overview in the body.

Fix or remove the dangling 'resources/implementation-playbook.md' reference — the path does not exist in the bundle.

Delete the generic 'Use this skill when' / 'Do not use' / 'Instructions' boilerplate and replace it with specific binary-analysis workflow guidance, including validation checkpoints (e.g. verify recovered signatures against cross-references).

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code blocks, but the generic 'Use this skill when' / 'Instructions' boilerplate ('Clarify goals, constraints, and required inputs') and a textbook dump of standard assembly patterns Claude largely already knows add unnecessary tokens.	3 / 5
Actionability	Provides concrete, executable assembly patterns and runnable Ghidra (Java) and IDA Pro (IDAPython) scripts covering common analysis cases, with only minor gaps.	4 / 5
Workflow Clarity	The 7-step 'Analysis Workflow' gives a clear sequence but includes no validation checkpoints or feedback loops; the operation is read-only so the destructive-batch cap does not apply, leaving it at the no-checkpoint anchor.	3 / 5
Progressive Disclosure	A ~450-line inline reference dump that clearly belongs in split files (Ghidra tips, IDA patterns) is inlined, and its only external reference points to 'resources/implementation-playbook.md' which does not exist in the bundle.	2 / 5
	Total	12 / 20 Passed

Description

53%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 clearly written in third person and names a distinct domain with a few concrete actions, but it omits any explicit 'when to use' trigger guidance and leans on generic 'comprehensive patterns and techniques' padding. Adding a concrete Use-when clause and more natural trigger terms would lift it.

Suggestions

Append an explicit trigger clause, e.g. 'Use when analyzing compiled binaries, reading assembly, or reconstructing program logic from a binary.'

Replace 'Comprehensive patterns and techniques for' with more concrete actions (e.g. 'Identify calling conventions, recover data structures, and decompile functions') to improve specificity.

Add natural synonyms users actually say — 'reverse engineering', 'disassembly', 'decompilation', 'RE' — to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and three actions ('analyzing compiled binaries, understanding assembly code, and reconstructing program logic'), but the leading 'Comprehensive patterns and techniques for' is generic padding and coverage is not comprehensive — no tools or decompilation specifics.	3 / 5
Completeness	Clearly states what the skill does but provides no 'Use when...' trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Includes relevant keywords ('binary analysis', 'assembly code', 'compiled binaries') but misses common natural variations a user would say such as 'reverse engineering', 'disassembly', 'decompilation', or 'malware analysis'.	3 / 5
Distinctiveness Conflict Risk	'binary analysis' is a clearly distinct niche with minimal conflict risk, though it could marginally overlap with adjacent reverse-engineering or malware-analysis skills.	4 / 5
	Total	13 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/binary-analysis-patterns/SKILL.md
Commit: 1f67c44

Reviewed: about 15 hours 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.