binary-analysis-patterns

Master binary analysis patterns including disassembly, decompilation, control flow analysis, and code pattern recognition. Use when analyzing executables, understanding compiled code, or performing static analysis on binaries.

Quality

90%

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

Quality

Content

80%

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

The body is a well-organized, executable pattern catalog with lean prose and concrete code, scoring high on conciseness and actionability. Its weaknesses are the lack of validation/feedback checkpoints in the analysis workflow and the absence of any progressive disclosure into separate reference files despite the large size.

Suggestions

Add explicit validation checkpoints to the Analysis Workflow (e.g., verify reconstructed types against cross-references before documenting, re-run pattern scripts and confirm output), and a brief feedback loop for when a pattern assumption does not hold.

Split the large single-file content into one-level-deep references (e.g., x86-64/ARM patterns, Ghidra tips, IDA Pro patterns as separate files under references/) and keep SKILL.md as a concise overview with signaled links, improving progressive disclosure.

Consider trimming or relocating the introductory "Use this skill when / Do not use this skill when / Instructions" boilerplate, which is generic and adds tokens without domain-specific value.

Dimension	Reasoning	Score
Conciseness	The body is lean reference material that assumes Claude knows assembly basics — one-line section intros followed by concrete code, with no padded explanations of basic concepts like what a binary or library is, matching the lean-and-efficient anchor.	3 / 3
Actionability	It provides copy-paste-ready code across assembly, IDAPython, Ghidra Java, and Python scripts that are concrete and executable rather than pseudocode, matching the fully-executable anchor.	3 / 3
Workflow Clarity	The "Analysis Workflow" section lists a clear 7-step sequence, but there are no validation checkpoints or error-recovery feedback loops within it; this matches the anchor where steps are present but checkpoints are missing or implicit, so it is not 3.	2 / 3
Progressive Disclosure	At roughly 450 lines the skill is a single monolithic file with clear section headers but no one-level-deep references to separate files for the tool-specific or arch-specific content that could be split out; it is not 1 because organization is good and there are no nested references, but not 3 because nothing is offloaded to referenced bundle files.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 distinctive: it lists concrete capabilities and pairs them with an explicit "Use when" trigger using natural user-facing terms. Voice is appropriately third-person/imperative, so no voice penalty applies.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "disassembly, decompilation, control flow analysis, and code pattern recognition" — matching the anchor that lists several specific concrete actions rather than a single vague domain reference.	3 / 3
Completeness	It explicitly answers what (disassembly, decompilation, control flow analysis, code pattern recognition) and when via an explicit "Use when..." clause, matching the anchor that requires both with explicit triggers; not 2 because the when is explicit rather than merely implied.	3 / 3
Trigger Term Quality	Triggers like "analyzing executables, understanding compiled code, or performing static analysis on binaries" are natural phrasings a user would say when requesting this skill, giving good coverage of natural terms rather than only technical jargon.	3 / 3
Distinctiveness Conflict Risk	Binary analysis is a clear niche with distinct triggers (executables, compiled code, binaries) unlikely to fire for unrelated skills, matching the clear-niche anchor rather than the overlapping-skill anchor.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/binary-analysis-patterns/SKILL.md
Commit: e63f7dd

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