reverse-engineering

Name: reverse-engineering
Availability: InStock
Author: ashwnn

Analyze binary artifacts using static analysis, dynamic instrumentation, and vulnerability identification.

Updated Aug 23, 2026

Search Tags:#static-analysis #reverse-engineering #frida #ghidra #dynamic-analysis #binary-analysis #vulnerability-identification

Ready to run

npx skills add https://github.com/ashwnn/agent-config --skill reverse-engineering-ashwnn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reverse-engineering
Source: https://github.com/ashwnn/agent-config/tree/main/skills/reverse-engineering
Command: npx skills add https://github.com/ashwnn/agent-config --skill reverse-engineering-ashwnn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Binary analysis is often ad-hoc, brittle, and error-prone; this Skill provides a structured methodology for analyzing binaries, firmware, or obfuscated code in authorized environments.

Core Features & Use Cases

Static analysis setup and artifact discovery with Ghidra/objdump workflows.
Dynamic instrumentation guidance using Frida for runtime observations.
Vulnerability identification through function review, pattern search, and documentation.

Quick Start

Provide a binary sample in an authorized environment and begin with Phase 1 triage to initiate analysis.

Frequently Asked Questions about reverse-engineering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I start binary analysis on an unknown executable sample?▼

Begin binary analysis by providing a sample in an authorized environment and initiating Phase 1 triage to discover artifacts. The workflow guides you through static analysis setup and artifact discovery using tools like Ghidra and objdump.

Can I use Frida for dynamic instrumentation during binary analysis?▼

Yes, Frida is supported for dynamic instrumentation during binary analysis. The workflow provides specific guidance on using Frida for runtime observations to complement static analysis and understand obfuscated code behavior.

What is the best way to identify vulnerabilities in firmware through reverse-engineering?▼

Identify vulnerabilities in firmware by applying a structured reverse-engineering workflow that includes function review, pattern search, and documentation. This methodology adapts to firmware formats and obfuscated code scenarios for thorough analysis.

How does static analysis compare to dynamic analysis for understanding obfuscated code?▼

Static analysis examines the binary without execution using Ghidra to map structure, while dynamic analysis uses Frida for runtime observations. Combining both provides a comprehensive understanding of obfuscated code and its actual behavior.

Do I need a specific environment setup to analyze obfuscated binaries?▼

Yes, you need an authorized environment to safely analyze obfuscated binaries and firmware. The structured workflow assumes proper setup to perform static artifact discovery and dynamic instrumentation without unintended system impact.

Why does my ad-hoc binary analysis workflow keep missing vulnerabilities?▼

Ad-hoc binary analysis is brittle and error-prone, often missing vulnerabilities due to lack of structure. Applying a structured reverse-engineering workflow with checklists and best practices ensures systematic function review and pattern search.