Investigate stuck runs and execution failures by tracing Symphony and Codex logs with issue/session identifiers; use when runs stall, retry repeatedly, or fail unexpectedly.
88
88%
Does it follow best practices?
Impact
83%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Log investigation script and report for stuck run
Uses rg not grep
0%
0%
rg -n flag
0%
0%
Searches log/symphony.log*
0%
0%
issue_identifier first
50%
75%
session_id extraction
60%
50%
Traces session by session_id
62%
87%
Lifecycle reading
100%
100%
Failure classification
100%
100%
Exact failing stage
100%
100%
Evidence with correlation fields
100%
90%
Multiple sessions noted
100%
100%
Stall/backoff signals cited
100%
100%
Incident report for repeated app-server startup failure
App-server startup classification
100%
100%
Pre-stream failure stage
100%
100%
All three session IDs identified
100%
100%
issue_id paired with findings
100%
100%
issue_identifier in evidence
100%
100%
session_id in evidence
100%
100%
Timestamps in evidence
100%
100%
Scope: isolated to MT-714
100%
100%
Scheduling retry signals cited
100%
100%
Root cause recorded
100%
100%
No mixing concurrent sessions
100%
100%
Multi-ticket scope analysis for worker crash pattern
Uses rg not grep
0%
0%
rg -n flag used
0%
0%
Failure signal search
100%
100%
Worker crash classification
100%
100%
Agent task exited signal cited
100%
100%
Systemic conclusion
100%
100%
Successful tickets noted
100%
100%
Both failing tickets covered
100%
100%
issue_identifier in evidence
100%
100%
session_id in evidence
100%
100%
Timestamps in evidence
100%
100%
Searches log/symphony.log*
42%
42%
4cbe3a9
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.