binary-analysis-patterns

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

Quality

42%

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

35%Weight 40%Scale 1-3

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

The body is an extensive, well-organized catalog of assembly and tool-scripting patterns, but it spends most of its tokens restating concepts Claude already knows and offers little task-oriented guidance. Its single progressive-disclosure reference points to a file that does not exist.

Suggestions

Trim the basic assembly primer (calling conventions, prologues, loops, bit ops) to only the non-obvious patterns Claude would not already know, and move the rest into a reference file.

Make the 'Analysis Workflow' a real procedure with explicit validation checkpoints (e.g., confirm architecture/endianness before disassembling, verify recovered signatures against call sites).

Create the referenced `resources/implementation-playbook.md` (or remove the dangling reference) and split the Ghidra/IDA scripting examples into separate reference files with clearly signaled links.

Dimension	Reasoning	Score
Conciseness	The ~450-line body catalogs calling conventions, function prologues, loop/switch patterns, bit manipulation, and array/struct access — basic programming concepts Claude already knows — padded out as a reference dump.	1 / 3
Actionability	It contains concrete code (real IDAPython and Ghidra scripts, assembly idioms like `lea eax, [rax + rax*2]`), but several examples use pseudo-syntax (`mov rdi, [a]`, `mov [rsp+0x20], [e]`) and the material is illustrative reference rather than task-oriented executable workflow.	2 / 3
Workflow Clarity	The 'Analysis Workflow' lists a 7-step sequence (triage, string analysis, function identification, ...) but includes no validation checkpoints or feedback loops, and the 'Instructions' section only abstractly says to 'validate outcomes'.	2 / 3
Progressive Disclosure	Content is well-sectioned but delivered as a single monolithic inline wall; the one external reference (`resources/implementation-playbook.md`) is a dangling path — no `resources/` directory exists.	2 / 3
	Total	7 / 12 Passed

Description

50%Weight 40%Scale 1-3

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 conveys a clear domain and a few actions but relies on abstract verbs and omits any 'Use when' trigger guidance. It is distinguishable but not sharply differentiated from broader code-analysis skills.

Suggestions

Add an explicit 'Use when ...' trigger clause naming concrete situations (e.g., reverse engineering a binary, decompiling, reading disassembly, analyzing malware).

Replace abstract verbs with concrete actions: 'disassemble functions, recover types, identify calling conventions, and reconstruct control flow'.

Include the natural trigger terms users actually say — 'reverse engineering', 'decompile', 'disassembly', 'IDA Pro/Ghidra analysis'.

Dimension	Reasoning	Score
Specificity	Names the binary-analysis domain and three actions ('analyzing compiled binaries', 'understanding assembly code', 'reconstructing program logic'), but the verbs are abstract goals rather than concrete operations like 'disassemble', 'decompile', or 'identify functions'.	2 / 3
Completeness	It states what the skill covers but provides no 'Use when...' trigger clause, so the 'when' is entirely missing — capping completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	It includes some natural terms ('compiled binaries', 'assembly code') but omits the most common user phrasings such as 'reverse engineering', 'decompile', 'disassembly', or 'malware analysis'.	2 / 3
Distinctiveness Conflict Risk	Binary analysis is a recognizable niche, but the description lacks explicit distinguishing triggers and the generic verbs could overlap with general code-analysis skills.	2 / 3
	Total	8 / 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
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: c0bd5d6

Reviewed: 7 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.