CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

62

Quality

53%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/binary-analysis-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

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 and common tool/format references that users might mention when needing this skill.

Suggestions

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

Consider including tool-related terms users might mention such as 'IDA', 'Ghidra', 'objdump', or 'radare2'

DimensionReasoningScore

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 is essentially a table of contents with no substantive content in the main file. It lacks any concrete binary analysis patterns, code examples, or actionable guidance—everything is deferred to sub-skills without providing even a basic overview or quick-start examples. The generic boilerplate instructions add no value for binary analysis specifically.

Suggestions

Add at least 2-3 concrete, executable examples of common binary analysis patterns (e.g., identifying a function prologue, recognizing a loop construct) directly in the main skill file

Include a quick-start workflow section showing the typical sequence for analyzing an unknown binary (load → identify entry points → trace control flow → etc.) with specific tool commands

Replace the generic 'Instructions' section with binary-analysis-specific guidance, such as which tools to use (objdump, radare2, Ghidra) with actual command examples

Add a brief summary of what each sub-skill category covers so users can navigate without opening 19 separate files

DimensionReasoningScore

Conciseness

The content is relatively lean but includes some unnecessary boilerplate (generic 'Use this skill when' and 'Do not use this skill when' sections that add little value). The instructions section is vague filler rather than actionable content.

2 / 3

Actionability

The skill provides no concrete code, commands, or executable examples. It's entirely a table of contents pointing to sub-skills with no actual binary analysis guidance, patterns, or techniques in the main file itself.

1 / 3

Workflow Clarity

No workflow is defined despite 'Analysis Workflow' being listed as a sub-skill. The main file provides no sequencing, validation steps, or process guidance for binary analysis tasks.

1 / 3

Progressive Disclosure

The structure attempts progressive disclosure with 19 sub-skill references, but the main file provides almost no overview content—it's essentially just a link index. There's no quick-start content or summary of key patterns before diving into references.

2 / 3

Total

6

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
Dokhacgiakhoa/antigravity-ide
Reviewed

Table of Contents

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.