Trace Debuger

Use this skill to generate a self-contained Markdown trace debug report.

Inputs

• - trace_id (required)
• INLINECODE1 (optional, default http://127.0.0.1:16686)
• INLINECODE3 (optional, default http://127.0.0.1:9200)
• INLINECODE5 (optional, absolute path, default /Users/noodles/Desktop/code/go-components/examples/tracer)
• INLINECODE7 (optional, default ./trace_debug_report_{trace_id}.md)
• INLINECODE9 (optional, default filebeat-tracer-*)
• INLINECODE11 (optional, default 2000)

Run

CODEBLOCK0

Output

• - Writes Markdown report to INLINECODE13
• MUST send the generated Markdown report to the user as a file attachment via the chat window in the same session before finishing the task
• MUST send the report as ONE chat message only: attach the Markdown file and put the strict summary block in the same message caption/body.
• 【markdown报告文件】 is a placeholder and MUST be replaced with the real uploaded Markdown filename (example: trace_debug_report_<trace_id>.md).
• Use exactly this format in caption/body:

CODEBLOCK1

• - Prints fixed summary lines to stdout:

CODEBLOCK2

Notes

• - Keep logs sorted by timestamp ascending.
• After fetching ES logs, run Codex in repository root (automated via codex exec equivalent to TUI paste workflow) with this prompt:

• - If repository is provided, include code-context hints and file matches for suspected bug areas.
• If repository is not provided, base bug hypotheses on logs + spans only.
• After analysis in chat workflow: send the generated Markdown report as a file attachment to the user through the chat window, with the strict summary block in the same message caption/body (single message only).
• The first line must be the real Markdown filename (not placeholder text).
• Finally, delete the local Markdown file.