القائمة
Trace analysis expert for Mesen2 debugging. Captures execution logs, filters for key state changes (subroutines, RAM writes), and summarizes failure chains for expert consultation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use the Agentic File System (AFS) context model for discovery, mounts, scratchpad memory, and file-based tool workflows. Use when a task involves .context operations, AFS CLI usage, or cross-agent context coordination.
Read and interpret the Link to the Past (ALTTP) disassembly with label/symbol context. Use when mapping ROM/CPU addresses to labels, searching usdasm/jpdasm sources, or cross-referencing routines with Hyrule Historian, z3dk label indexes, or z3ed output.
Train, evaluate, and maintain the scawful-echo persona and related avatar models (Echo/Memory/Muse). Use when working on persona voice, dataset prep, A/B testing, deployment, or tool-calling constraints for avatar models.
Autonomous navigation agent for Oracle of Secrets. Uses static map data and dynamic RAM state to localize Link and route him to destinations.
End-to-end Oracle of Secrets debugging using the Mesen2-OOS socket CLI, z3ed, and label/symbol tooling. Use for breakpoint/trace capture, memory inspection, savestate repro, overlays, or crash/regression triage (replaces mesen2-mcp and legacy Lua bridge workflows).
Expert guidance for LLM model training, synthetic data generation (SDE), Hierarchical MoE (H-MoE) management, and agentic evaluation. Use when setting up training runs (Vast.ai), generating datasets, or performing technical research PDF analysis for ROM hacking and general AI development.
| name | trace-detective |
| description | Trace analysis expert for Mesen2 debugging. Captures execution logs, filters for key state changes (subroutines, RAM writes), and summarizes failure chains for expert consultation. |
z3ed debug trace.Use z3ed to pull the last N instructions or run forward with logging.
z3ed debug trace --count 5000 (Capture recent history).z3ed debug trace --start --condition "pc==0x8000" (Conditional trace).Raw traces are noisy (LDA, STA, ADC...). Filter for:
JSL, JML, RTS, RTL (Subroutine boundaries).$7E0010 (GameMode), $7E00A0 (RoomID), $7EF3CC (Follower).P (status register) indicating 8/16-bit mode desyncs.Translate opcode streams into "What happened":
"At frame 102, routine
LinkState_07was entered. It branched toDoorCheckbut read a0x00from$7EF3CC(Follower), leading to an infinite loop at$02804C."
Prepare a "Debug Context Pack" for Qwen/Claude:
trace-detective capture --frames 60 (while reproducing).trace-detective analyze --focus 7E0010 (Look for mode switches).trace-detective capture [--frames N]: Dump recent execution log.trace-detective analyze <logfile> [--focus ADDR]: Filter and summarize.trace-detective blame <addr>: Find the instruction that last wrote to ADDR.z3ed: Must be in PATH (from ~/src/hobby/yaze/build/bin/Debug/z3ed).Mesen2: Must be running with socket server active.z3ed can connect to Mesen2 socket. Check z3ed debug state.z3ed was built with debug features. Ensure emulation is running during capture.--focus or filtering to narrow down relevant instructions.