Works with the AI Agents you already use
fw analyzer
Binary-level firmware analyzer for crash resolution, stack depth estimation, and memory layout inspection.
Free
fw analyzer
Example session with this skill installed
Analyze the crash at 0x080015AC in firmware.axf and show me the memory layout of the 'SystemConfig' struct.
- Read your context and instructions
- Compiled the fw analyzer
I have analyzed the provided address and struct definition from firmware.axf. The crash address maps to an inlined function within the UART interrupt handler.
Firmware Analysis Report
Crash Address Resolution
0x080015AC: drivers/uart.c:142
└─ inlined from: include/buffer.h:22 (fifo_push)
└─ inlined from: src/main.c:88 (UART_IRQ_Handler)
Struct Layout: SystemConfig
| Member | Type | Offset | Size | Padding |
|---|---|---|---|---|
device_id | uint32_t | 0x0 | 4 | 0 |
status_flags | uint8_t | 0x4 | 1 | 3 |
buffer_ptr | void* | 0x8 | 4 | 0 |
mode | uint16_t | 0xC | 2 | 2 |
| Total Size | 16 bytes |
Next steps
- Check
drivers/uart.cat line 142 for potential null pointer dereferences in thefifo_pushcall. - Review
SystemConfigalignment; there are 5 bytes of padding that could be optimized by reordering members. - Run
--disasm UART_IRQ_Handler --mixedto see the exact instructions leading to the fault.
Connects securely to your tools. The creator never sees your data.
About this skill
Embedded systems development often hits a wall when the source code says one thing, but the binary behaves differently. This skill provides a read-only firmware analyzer that inspects .axf and ELF files to reveal exactly what the compiler produced, how memory is allocated, and why a crash occurred at a specific address.
What it does
- Crash resolution maps raw PC/LR addresses to source lines and full inline chains.
- Binary disassembly extracts machine code for specific functions with optional mixed source interleaving.
- Memory profiling ranks the largest functions and data objects by Flash and RAM usage.
- Struct inspection details the in-memory layout of C structs, including padding, bitfields, and member offsets.
- Stack analysis estimates stack frame sizes and calculates the deepest call-chain depth from any entry point.
- Dead code detection identifies static objects and functions that appear unreferenced in the linked binary.
How it works
- Load image by providing the path to a built
.axfor ELF file with DWARF debug info. - Query facts using specific flags for addresses, symbols, or struct names to extract post-link data.
- Analyze stacks by specifying entry points to walk the call tree and accumulate frame sizes.
- Audit budgets by supplying an optional JSON manifest to compare modeled usage against allocated limits.
Frameworks & tools
Works with ELF32/ELF64 files generated by ARMCC, ARMClang, or GCC. It requires Python 3.10 and pyelftools, with optional capstone support for disassembly.
Why this beats prompting it yourself
Generic AI models cannot see inside your binary artifacts or understand DWARF debug information. This skill acts as a bridge, pulling hard facts from the linked output that source-level analysis would miss, such as compiler-inserted padding or actual stack usage.
Use cases
- Debugging HardFault exceptions by resolving register values to specific source lines.
- Trimming firmware size by identifying large, unused, or redundant data objects.
- Verifying ABI and FPU configurations to ensure the build matches hardware capabilities.
- Estimating task stack requirements during RTOS integration or bare-metal development.
Known limitations
Does not support source-level semantics like macro expansion, include dependencies, or data flow. Requires DWARF debug info for high-level features like struct layout and stack analysis.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.
Requires ELF/DWARF input. Cannot analyze source-only semantics like macros or cyclomatic complexity. Stack analysis is a model, not a guaranteed runtime peak.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 10 days ago
- Free with an Agensi account
- Software
Python