ワンクリックでManusで任意のスキルを実行

trace-detective

スター0

フォーク0

更新日2026年1月28日 04:08

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 ページを確認してインストールできます。

Manusで実行

ソース

scawful

scawful/afs_scawful

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Trace Detective

Scope

Capture execution traces from Mesen2 via z3ed debug trace.
Analyze traces to identify crash vectors (infinite loops, invalid jumps, bad RAM writes).
Summarize low-level logs into high-level behavioral narratives.
Package context for expert debugging (handoffs to Qwen/Claude).

Core Capabilities

1. Trace Capture

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).

2. Signal Filtering

Raw traces are noisy (LDA, STA, ADC...). Filter for:

Control Flow: JSL, JML, RTS, RTL (Subroutine boundaries).
Key RAM: Writes to $7E0010 (GameMode), $7E00A0 (RoomID), $7EF3CC (Follower).
Registers: Sudden changes in P (status register) indicating 8/16-bit mode desyncs.

3. Narrative Generation

Translate opcode streams into "What happened":

"At frame 102, routine LinkState_07 was entered. It branched to DoorCheck but read a 0x00 from $7EF3CC (Follower), leading to an infinite loop at $02804C."

4. Expert Handoff

Prepare a "Debug Context Pack" for Qwen/Claude:

Trace Summary: The narrative above.
Relevant ASM: The source code for the routines identified in the trace.
Memory Snapshot: Values of key variables at the time of crash.

Workflow

Trigger: User says "The game crashed when I entered the door."
Capture: trace-detective capture --frames 60 (while reproducing).
Analyze: trace-detective analyze --focus 7E0010 (Look for mode switches).
Report: Generate markdown summary or prompt for the expert.

Commands

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.

Integration Dependencies

z3ed: Must be in PATH (from ~/src/hobby/yaze/build/bin/Debug/z3ed).
Mesen2: Must be running with socket server active.

Example Prompts

"Capture the last 60 frames of execution trace."
"Analyze the trace for any writes to GameMode ($7E0010)."
"Why did the game crash when I entered the dungeon?"
"Who wrote 0x00 to address $7EF3CC?"

Troubleshooting

Connection Failed: Ensure z3ed can connect to Mesen2 socket. Check z3ed debug state.
Empty Trace: Verify z3ed was built with debug features. Ensure emulation is running during capture.
Noise: Traces are verbose. Use --focus or filtering to narrow down relevant instructions.

このリポジトリの他の Skills

同じリポジトリ

agentic-context

scawful/afs_scawful

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.

2026-04-280

alttp-disasm-labels

scawful/afs_scawful

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.

2026-03-190

echo-persona

scawful/afs_scawful

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.

2026-03-190

hyrule-navigator

scawful/afs_scawful

Autonomous navigation agent for Oracle of Secrets. Uses static map data and dynamic RAM state to localize Link and route him to destinations.

2026-03-190

mesen2-oos-debugging

scawful/afs_scawful

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).

2026-03-190

model-training-expert

scawful/afs_scawful

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.

2026-03-190

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.

Trace Detective

Scope

Capture execution traces from Mesen2 via z3ed debug trace.
Analyze traces to identify crash vectors (infinite loops, invalid jumps, bad RAM writes).
Summarize low-level logs into high-level behavioral narratives.
Package context for expert debugging (handoffs to Qwen/Claude).

Core Capabilities

1. Trace Capture

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).

2. Signal Filtering

Raw traces are noisy (LDA, STA, ADC...). Filter for:

Control Flow: JSL, JML, RTS, RTL (Subroutine boundaries).
Key RAM: Writes to $7E0010 (GameMode), $7E00A0 (RoomID), $7EF3CC (Follower).
Registers: Sudden changes in P (status register) indicating 8/16-bit mode desyncs.

3. Narrative Generation

Translate opcode streams into "What happened":

"At frame 102, routine LinkState_07 was entered. It branched to DoorCheck but read a 0x00 from $7EF3CC (Follower), leading to an infinite loop at $02804C."

4. Expert Handoff

Prepare a "Debug Context Pack" for Qwen/Claude:

Trace Summary: The narrative above.
Relevant ASM: The source code for the routines identified in the trace.
Memory Snapshot: Values of key variables at the time of crash.

Workflow

Trigger: User says "The game crashed when I entered the door."
Capture: trace-detective capture --frames 60 (while reproducing).
Analyze: trace-detective analyze --focus 7E0010 (Look for mode switches).
Report: Generate markdown summary or prompt for the expert.

Commands

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.

Integration Dependencies

z3ed: Must be in PATH (from ~/src/hobby/yaze/build/bin/Debug/z3ed).
Mesen2: Must be running with socket server active.

Example Prompts

"Capture the last 60 frames of execution trace."
"Analyze the trace for any writes to GameMode ($7E0010)."
"Why did the game crash when I entered the dungeon?"
"Who wrote 0x00 to address $7EF3CC?"

Troubleshooting

Connection Failed: Ensure z3ed can connect to Mesen2 socket. Check z3ed debug state.
Empty Trace: Verify z3ed was built with debug features. Ensure emulation is running during capture.
Noise: Traces are verbose. Use --focus or filtering to narrow down relevant instructions.