binary-analysis-patterns

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

Quality

48%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/binary-analysis-patterns/SKILL.md

Quality

Discovery

32%

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 establishes a clear domain (binary analysis/reverse engineering) but lacks explicit trigger guidance and misses common user terminology. It reads more like a topic summary than actionable skill selection criteria, making it harder for Claude to know precisely when to invoke this skill versus related ones.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about reverse engineering, disassembling executables, analyzing malware, or understanding compiled code'.

Include common user terms and file extensions: 'reverse engineering', 'disassembly', 'decompilation', '.exe', 'ELF', 'PE files', 'IDA', 'Ghidra'.

Replace abstract 'patterns and techniques' with concrete actions: 'disassemble executables, identify function boundaries, analyze control flow, reconstruct source logic'.

Dimension	Reasoning	Score
Specificity	Names the domain (compiled binaries, assembly code) and some actions (analyzing, understanding, reconstructing program logic), but uses somewhat abstract terms like 'patterns and techniques' rather than listing concrete specific actions like 'disassemble executables, identify function boundaries, trace control flow'.	2 / 3
Completeness	Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this description has no 'when' component at all.	1 / 3
Trigger Term Quality	Includes relevant terms like 'binaries', 'assembly code', and 'program logic', but misses common variations users might say such as 'reverse engineering', 'disassembly', 'decompilation', 'malware analysis', 'executable', '.exe', 'ELF', or 'IDA'.	2 / 3
Distinctiveness Conflict Risk	The focus on 'compiled binaries' and 'assembly code' provides some distinctiveness from general code analysis skills, but could overlap with debugging skills, security analysis skills, or general programming skills without clearer boundaries.	2 / 3
	Total	7 / 12 Passed

Implementation

64%

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

This is a technically strong skill with excellent actionable code examples covering multiple architectures and tools. The main weaknesses are its length (could benefit from better progressive disclosure) and the lack of explicit validation checkpoints in the workflow section. The boilerplate 'Use this skill when' section adds little value for Claude.

Suggestions

Remove or condense the generic 'Use this skill when' and 'Do not use this skill when' sections, as they add little actionable value

Add explicit validation checkpoints to the Analysis Workflow section (e.g., 'Verify function boundaries before proceeding to data structure recovery')

Consider splitting architecture-specific patterns (ARM, x86-64) and tool-specific sections (Ghidra, IDA) into separate referenced files to improve progressive disclosure

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some redundant explanations (e.g., the generic 'Use this skill when' section adds little value). The assembly examples are dense and useful, but the overall document could be tightened by removing boilerplate sections.	2 / 3
Actionability	Provides extensive executable assembly code examples, concrete patterns for x86-64 and ARM, and specific IDAPython/Ghidra scripts. The code is copy-paste ready and covers real-world scenarios like calling conventions, loop patterns, and data structure access.	3 / 3
Workflow Clarity	The 'Analysis Workflow' section at the end provides a numbered sequence, but lacks explicit validation checkpoints or feedback loops. For binary analysis (which can involve destructive operations or complex multi-step processes), more explicit verification steps would strengthen this.	2 / 3
Progressive Disclosure	References 'resources/implementation-playbook.md' for detailed examples, which is good. However, the main document is quite long (monolithic) and could benefit from splitting detailed patterns (ARM, Ghidra, IDA) into separate referenced files with clearer navigation.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 9c177eb

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