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.

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/binary-analysis-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-5

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

A dense, executable pattern catalog with a clear multi-step analysis workflow, but it is a monolithic inline reference with no progressive file disclosure and a workflow lacking validation checkpoints; some boilerplate and basic re-explanation could be trimmed.

Suggestions

Split the large reference material into bundled files (e.g., references/ghidra-patterns.md, references/ida-patterns.md, references/asm-patterns.md) and keep SKILL.md as a concise overview that links one level deep into them.

Add explicit validation checkpoints to the Analysis Workflow (e.g., verify decompilation output against disassembly, confirm recovered function signatures against cross-references) with a fix-and-retry loop.

Remove the generic "Use this skill when / Do not use this skill when / Instructions" boilerplate and trim re-explanations of basics like calling-convention register lists that Claude already knows.

DimensionReasoningScore

Conciseness

The body is a dense, reference-style catalog of terse assembly snippets that mostly assumes Claude's competence, but generic boilerplate sections ("Use this skill when," "Instructions") and re-teaching of basics (calling-convention register lists, struct padding) keep it from being fully lean.

3 / 5

Actionability

Provides concrete, mostly copy-paste-ready assembly snippets and runnable Ghidra/IDAPython scripts covering common cases, though several examples are schematic templates with placeholder labels (skip_block, [a]) rather than fully concrete programs.

4 / 5

Workflow Clarity

The 7-step "Analysis Workflow" gives a clear, well-defined sequence backed by a "Common Pitfalls" list, but it lacks explicit validation checkpoints or feedback loops for verifying analysis results.

3 / 5

Progressive Disclosure

The skill has section headers providing some navigable structure, but at ~450 lines the entire pattern catalog, Ghidra scripts, and IDA patterns are inlined into SKILL.md with no references to separate files.

3 / 5

Total

13

/

20

Passed

Description

92%Weight 40%Scale 1-5

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

A strong, specific description that names concrete capabilities and provides explicit use-when triggers with natural language. The only gap is the absence of common synonyms such as "reverse engineering" and typical binary file extensions.

DimensionReasoningScore

Specificity

Lists multiple specific concrete analysis techniques — "disassembly, decompilation, control flow analysis, and code pattern recognition" — giving comprehensive coverage of the binary-analysis domain rather than minor gaps.

5 / 5

Completeness

Explicitly answers both what ("Master binary analysis patterns including disassembly, decompilation...") and when ("Use when analyzing executables, understanding compiled code, or performing static analysis on binaries") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage with "analyzing executables, understanding compiled code, or performing static analysis on binaries," but missing common synonyms like "reverse engineering" and binary file extensions (.exe, .elf).

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (static analysis of compiled binaries) with distinct triggers that are unlikely to fire for unrelated skills, presenting minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rmyndharis/antigravity-skills
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.