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.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill binary-analysis-patternsOverall
score
82%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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-crafted skill description that follows best practices. It uses third person voice, lists specific concrete capabilities, includes a clear 'Use when...' clause with natural trigger terms, and occupies a distinct niche in binary/reverse engineering analysis that won't conflict with other skills.
| 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 ('Master binary analysis patterns including disassembly, decompilation, control flow analysis, and 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 natural keywords users would say: 'binary analysis', 'disassembly', 'decompilation', 'executables', 'compiled code', 'static analysis', 'binaries' - good coverage of terms a reverse engineer or security analyst would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on binary/executable analysis with distinct triggers like 'disassembly', 'decompilation', 'executables', 'binaries' - unlikely to conflict with general code analysis or document processing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, concrete binary analysis patterns with excellent assembly examples and tool-specific scripts. However, it's overly comprehensive for a single file, lacking progressive disclosure structure, and the workflow section needs explicit validation checkpoints for complex analysis tasks.
Suggestions
Split detailed content into separate files (e.g., X86_PATTERNS.md, ARM_PATTERNS.md, GHIDRA_TIPS.md) and make SKILL.md an overview with clear navigation links
Add explicit validation checkpoints to the Analysis Workflow section (e.g., 'Verify function boundaries before proceeding to data structure recovery')
Remove the generic 'Use this skill when / Do not use' boilerplate sections that add no value for Claude
Consider trimming redundant examples - the calling convention section could show one convention in detail and reference others
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is comprehensive but includes some unnecessary sections like generic 'Use this skill when' boilerplate and explanations that could be trimmed. The assembly examples are dense and useful, but the sheer volume (400+ lines) could be more selective. | 2 / 3 |
Actionability | Excellent concrete, executable examples throughout. Assembly code snippets are real and copy-paste ready, Python/Java scripts for Ghidra and IDA are functional, and patterns show exact instruction sequences with clear comments explaining each line. | 3 / 3 |
Workflow Clarity | The 'Analysis Workflow' section at the end provides a numbered sequence, but lacks validation checkpoints or feedback loops. For binary analysis (which can involve destructive operations or complex multi-step processes), explicit verification steps are missing. | 2 / 3 |
Progressive Disclosure | References 'resources/implementation-playbook.md' but the main content is a monolithic document with all patterns inline. The extensive assembly patterns, Ghidra tips, and IDA patterns could be split into separate reference files with the SKILL.md serving as an overview. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
88%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
- 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.