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

53%

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

Quality

Discovery

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-structured skill description that clearly defines its domain (binary analysis) with specific capabilities and explicit usage triggers. The main weakness is the trigger term coverage, which could benefit from additional natural language variations that users commonly employ when discussing reverse engineering tasks.

Suggestions

Add common user terms like 'reverse engineering', 'RE', 'malware analysis', '.exe files', 'ELF', 'PE format' to improve trigger term coverage

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'disassembly, decompilation, control flow analysis, and code pattern recognition' - these are distinct, technical capabilities that clearly describe what the skill does.	3 / 3
Completeness	Clearly answers both what ('disassembly, decompilation, control flow analysis, code pattern recognition') and when ('Use when analyzing executables, understanding compiled code, or performing static analysis on binaries') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes relevant terms like 'executables', 'compiled code', 'static analysis', 'binaries', but missing common variations users might say such as 'reverse engineering', 'RE', 'malware analysis', 'ELF', 'PE files', '.exe', or 'IDA'.	2 / 3
Distinctiveness Conflict Risk	Binary analysis is a clear niche with distinct triggers like 'disassembly', 'decompilation', 'executables', and 'binaries' - unlikely to conflict with general code analysis or document processing skills.	3 / 3
	Total	11 / 12 Passed

Implementation

22%

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

This skill functions primarily as a table of contents rather than actionable guidance. It lacks any concrete binary analysis techniques, code examples, or workflow guidance in the main file. The extensive sub-skill references suggest good organization potential, but the main skill provides no standalone value or context for when/how to use each module.

Suggestions

Add a quick-start section with at least one concrete binary analysis example (e.g., identifying a function prologue pattern or basic disassembly command)

Define a clear analysis workflow showing the typical sequence: load binary → identify architecture → analyze entry points → trace control flow → etc., with validation checkpoints

Add brief descriptions to each sub-skill link explaining what it covers and when to use it (e.g., 'x86-64 Instruction Patterns - Use for analyzing Windows/Linux x64 binaries')

Remove or condense the generic 'Use this skill when' boilerplate and replace with domain-specific guidance

Dimension	Reasoning	Score
Conciseness	The content is relatively brief but includes boilerplate sections ('Use this skill when', 'Do not use this skill when') that add little value and repeat obvious information. The instructions section is generic rather than domain-specific.	2 / 3
Actionability	No concrete code, commands, or executable examples are provided. The instructions are vague ('Clarify goals', 'Apply relevant best practices') and the main content is just a list of links to sub-skills without any actual binary analysis guidance.	1 / 3
Workflow Clarity	No workflow is defined despite binary analysis being inherently multi-step. There's no sequence, no validation checkpoints, and no guidance on how to approach analysis tasks or when to use which sub-skill.	1 / 3
Progressive Disclosure	The skill does reference 19 sub-skills and a playbook, showing intent for progressive disclosure. However, there's no overview content explaining what each sub-skill covers or how they relate, making navigation difficult without clicking through each link.	2 / 3
	Total	6 / 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: Dokhacgiakhoa/antigravity-ide
Commit: 3395991

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