What problem does it solve? When debugging z88dk-compiled programs, you often need to see what machine code actually landed at a given address, verify opcode generation for a specific CPU variant, or compare two builds at the binary level. This Skill guides the use of the z88dk-dis disassembler to inspect linked binaries with symbol context. ## Core Features & Use Cases - Multi-CPU disassembly: Supports z80, z180, z80n, ez80, Rabbit, R800, Game Boy z80, 8080, 8085, and KC160 via the -m flag family. - Symbol-aware output: Load map/symbol files with -x so disassembly shows named labels at the correct load, start, and end addresses. - Methodology guidance: Know when to prefer assembler listings (z88dk-z80asm -l) for verifying synthetic instruction expansion in library sources versus disassembling linked binaries. - Use Case: You suspect an 8085 build emitted wrong opcodes for a synthetic instruction. Disassemble the binary with -m8085 and a map file, or generate an assembler listing to confirm the expanded bytes. ## Quick Start Disassemble my program.bin for the z80 target starting at address 0x8000 using the symbols from program.map.