troubleshoot Skill
Investigate unexpected chat agent behavior by analyzing direct debug logs in JSONL files. Use when users ask why something happened, why a request was slow, why tools or subagents were used or skipped, or why instructions/skills/agents did not load. Published by microsoft in vscode.
What is troubleshoot Skill?
Investigate unexpected chat agent behavior by analyzing direct debug logs in JSONL files. Use when users ask why something happened, why a request was slow, why tools or subagents were used or skipped, or why instructions/skills/agents did not load. Published by microsoft in vscode. 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.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Data analysis
- Data analysis use cases
Technical details
- Install or run with Copy skill directory
When to use troubleshoot Skill
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode
- Skill file: extensions/copilot/assets/prompts/skills/troubleshoot/SKILL.md
What it does
Investigate unexpected chat agent behavior by analyzing direct debug logs in JSONL files. Use when users ask why something happened, why a request was slow, why tools or subagents were used or skipped, or why instructions/skills/agents did not load.
Skill instructions
Troubleshoot Purpose This skill investigates and explains unexpected chat agent behavior using direct log files. Use this skill for questions like: - Why did this request take so long? - Why was a tool or subagent called? - Why did instruction/skill/agent files not load? - Why was a tool call blocked or failed? - Why did the model not follow expectations? Base conclusions on evidence from logs. Do not guess. Data Source - Target session log directory/directories for analysis: {{VSCODETARGETSESSIONLOG}} Use direct debug log files written by Copilot Chat: debug-logs/<sessionId/ main.jsonl — always start here; primary conversation log models.json — (optional) snapshot of available models at session start systemprompt0.json — (optional) full system prompt sent to the model (untruncated) systemprompt1.json — (optional) written when the model changes mid-session tools0.json — (optional) tool definitions sent to the model tools1.json — (optional) written when the model changes mid-session run
Explore related resources
Frequently asked questions
What is troubleshoot?
troubleshoot is a open-source AI agent skill with Copy skill directory. Investigate unexpected chat agent behavior by analyzing direct debug logs in JSONL files.
Who is troubleshoot best for?
troubleshoot is best for reusing agent instructions, scripts, and references, data analysis workflows.
How do I install troubleshoot?
Install or run troubleshoot using Copy skill directory. Check troubleshoot for the latest setup command.
Is troubleshoot actively maintained?
troubleshoot may need a closer maintenance check before production use.
Auto-fetched from GitHub.
