binary-analysis-patterns

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

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/binary-analysis-patterns/SKILL.md

The canonical home for this skill is binary-analysis-patterns in sickn33/agentic-awesome-skills

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.

The body is a well-organized, actionable reference catalog of assembly and tool-scripting patterns, but it inlines material that belongs in separate reference files, points to a non-existent resource, and provides a workflow without validation checkpoints.

Suggestions

Move the bulk of the pattern catalog (disassembly, control-flow, data-structure sections) into a reference file under references/ and keep SKILL.md as a concise overview with one-level-deep links.

Create the referenced resources/implementation-playbook.md or remove the dangling pointer so navigation does not dead-end.

Add explicit validation/verification checkpoints to the Analysis Workflow (e.g. confirm function boundaries, verify recovered types against cross-references) with a fix-and-retry loop.

Trim the generic 'Instructions' boilerplate and the basic concept explanations (prologue/epilogue, simple loops) that Claude already knows to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The pattern catalog is mostly lean code with terse comments, but it re-explains basics Claude already knows (prologue/epilogue, calling conventions, simple if/loop patterns) and includes a generic boilerplate 'Instructions' section, so it sits in the mostly-efficient-with-some-unnecessary-explanation band.	3 / 5
Actionability	Concrete, copy-paste-ready assembly snippets and executable Ghidra/IDAPython scripts cover common cases, with only minor gaps where patterns are illustrative rather than complete runnable programs.	4 / 5
Workflow Clarity	The 'Analysis Workflow' lists a 7-step sequence, but there are no validation checkpoints or feedback loops between steps, leaving the sequence present yet checkpoint-implicit.	3 / 5
Progressive Disclosure	Section structure is decent, but the large pattern catalog is inlined entirely in SKILL.md and the one referenced file 'resources/implementation-playbook.md' does not exist, so references are present but not actually backed by a bundle.	3 / 5
	Total	13 / 20 Passed

Description

53%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.

The description identifies a clear domain and a few concrete actions but lacks any explicit 'when to use' trigger guidance and leans on abstract verbs. Adding natural user-facing trigger phrases would lift the completeness and trigger-term dimensions.

Suggestions

Append an explicit 'Use when...' clause naming concrete triggers such as reverse engineering a binary, reading disassembly, recovering function signatures, or working with Ghidra/IDA.

Swap abstract verbs for specific techniques (disassembly, decompilation, calling-convention analysis, structure recovery) to raise specificity.

Include natural synonyms and file formats users say (reverse engineering, disassembly, decompilation, ELF, PE, .exe) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the binary-analysis domain with a few concrete actions ('analyzing compiled binaries', 'understanding assembly code', 'reconstructing program logic'), but the verbs are abstract rather than enumerating specific techniques, so it stops at the domain-plus-1-2-actions band.	3 / 5
Completeness	It clearly states what the skill covers, but there is no 'Use when...' clause or equivalent trigger guidance, so per the rubric a missing 'when' caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant keywords like 'compiled binaries' and 'assembly code' appear, but common natural synonyms users would say (e.g. 'reverse engineering', 'disassembly', 'decompilation', '.exe', 'ELF') are missing.	3 / 5
Distinctiveness Conflict Risk	The binary-analysis / assembly niche is fairly distinct with limited overlap risk against unrelated skills, though it could overlap with adjacent reverse-engineering skills, keeping it just below 5.	4 / 5
	Total	13 / 20 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/binary-analysis-patterns/SKILL.md
Commit: 57c135b

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