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.
78
Quality
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/skills/binary-analysis-patterns/SKILL.mdQuality
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
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid reference skill with excellent actionable code examples covering x86-64, ARM, and common analysis patterns. The main weaknesses are its length (could benefit from better progressive disclosure) and the lack of explicit validation/verification steps in the workflow section. The generic boilerplate at the top adds little value.
Suggestions
Remove or minimize the generic 'Use this skill when' and 'Do not use this skill when' boilerplate sections that don't add binary-analysis-specific value
Add explicit validation checkpoints to the Analysis Workflow section (e.g., 'Verify function boundaries are correct before proceeding to data structure recovery')
Split tool-specific content (Ghidra, IDA Pro) into separate reference files and link from the main skill with clear navigation
| 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 overall document is quite long. | 2 / 3 |
Actionability | Excellent concrete examples throughout with executable assembly code, Python scripts for Ghidra and IDA Pro, and specific patterns with clear annotations. The code is copy-paste ready and well-commented. | 3 / 3 |
Workflow Clarity | The 'Analysis Workflow' section provides a numbered sequence, but lacks validation checkpoints or feedback loops. For binary analysis where mistakes can lead to incorrect conclusions, explicit verification steps would improve this. | 2 / 3 |
Progressive Disclosure | References 'resources/implementation-playbook.md' for detailed examples, but the main document is quite long and monolithic. Content like Ghidra/IDA scripts could be split into separate reference files with clearer navigation. | 2 / 3 |
Total | 9 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- duclm1x1/Dive-Ai
- Commit
20ba150
- 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.