binary-analysis-patterns

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The content is highly actionable with concrete assembly and tool-scripting examples and a clear analysis workflow, but it is verbose, restates familiar concepts, keeps everything inline, and contains a dangling file reference. It would benefit from trimming boilerplate and splitting detailed references into real bundle files.

Suggestions

Trim generic boilerplate in the 'Instructions' and 'Use this skill when' sections and remove restatements of standard assembly knowledge Claude already has.

Either create the referenced 'resources/implementation-playbook.md' or remove the dangling reference, and split large catalogs (Ghidra/IDA tips) into separate reference files with clear links.

Add explicit validation/feedback checkpoints to the analysis workflow so each phase confirms its output before proceeding.

Dimension	Reasoning	Score
Conciseness	The body is well-organized but restates standard knowledge Claude already has (calling conventions, prologues) and includes generic filler such as 'Clarify goals, constraints, and required inputs' and 'Apply relevant best practices', so it is mostly efficient but could be tightened.	2 / 3
Actionability	Provides numerous concrete, executable examples — assembly pattern blocks, Ghidra Java snippets, and IDAPython scripts — that are copy-paste ready, matching the anchor for fully executable guidance.	3 / 3
Workflow Clarity	The 'Analysis Workflow' section gives a clear 7-step sequence, but there are no explicit validation checkpoints or feedback loops between steps, leaving the sequence present but checkpoints implicit.	2 / 3
Progressive Disclosure	Sections are clearly organized, but the ~250-line body is monolithic with content (Ghidra/IDA tips, pattern catalogs) that could live in separate files, and the one reference to 'resources/implementation-playbook.md' points to a non-existent file.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 names concrete capabilities in a clear, third-person niche but lacks an explicit 'Use when' trigger and misses common user terms like 'reverse engineering'. It is strong on specificity and distinctiveness, weaker on trigger guidance and completeness.

Suggestions

Add an explicit 'Use when...' clause naming when Claude should invoke this skill (e.g., 'Use when reverse engineering, disassembling, or decompiling compiled binaries').

Broaden trigger terms to include natural user phrasings like 'reverse engineering', 'decompilation', and 'disassembly'.

Dimension	Reasoning	Score
Specificity	Quotes 'analyzing compiled binaries, understanding assembly code, and reconstructing program logic' — three named concrete actions within the domain, matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Clearly answers 'what' the skill does but provides no 'Use when...' trigger clause; per the rubric guideline a missing explicit trigger caps completeness at 2 rather than the level above.	2 / 3
Trigger Term Quality	Includes natural terms like 'binary analysis', 'compiled binaries', and 'assembly code', but omits the most common user phrasing such as 'reverse engineering', 'decompilation', or 'disassembly', so coverage of variations is incomplete.	2 / 3
Distinctiveness Conflict Risk	The binary-analysis / assembly niche is clearly scoped with distinct triggers and is unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 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
Commit: 5e71bba

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