debug Skill
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. Published by openai in symphony.
Decision snapshot
Is this a fit?
Documentation, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
27 days ago · Apache-2.0 license
No specific cautions were detected. Review the source and requested permissions before installing.
What is debug Skill?
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. Published by openai in symphony. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Documentation use cases
Declared skill metadata
- Source file: .codex/skills/debug/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use debug Skill
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/symphony
- Skill file: .codex/skills/debug/SKILL.md
What it does
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.
Skill instructions
Debug Goals - Find why a run is stuck, retrying, or failing. - Correlate Linear issue identity to a Codex session quickly. - Read the right logs in the right order to isolate root cause. Log Sources - Primary runtime log: log/symphony.log - Default comes from SymphonyElixir.LogFile (log/symphony.log). - Includes orchestrator, agent runner, and Codex app-server lifecycle logs. - Rotated runtime logs: log/symphony.log - Check these when the relevant run is older. Correlation Keys - issueidentifier: human ticket key (example: MT-625) - issueid: Linear UUID (stable internal ID) - sessionid: Codex thread-turn pair (<threadid-<turnid) elixir/docs/logging.md requires these fields for issue/session lifecycle logs. Use them as your join keys during debugging. Quick Triage (Stuck Run) 1. Confirm scheduler/worker symptoms for the ticket. 2. Find recent lines for the ticket (issueidentifier first). 3. Extract sessionid from matching lines. 4. Trace that sessionid across start, stream, completion/f
Verified compatibility and discovery
Frequently asked questions
What is debug?
debug is a open-source AI agent skill with Copy skill directory. 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.
Who is debug best for?
debug is best for reusing agent instructions, scripts, and references, documentation workflows.
How do I install debug?
Install or run debug using Copy skill directory. Check debug for the latest setup command.
Is debug actively maintained?
debug may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
