troubleshoot
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.
69
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Low
Low-risk findings.
2 low severity findings. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
This skill’s required workflow reads Copilot Chat debug logs from a provided session log directory (including `main.jsonl` and `system_prompt_*.json` / `tools_*.json`), and those files can contain outsider-authored free text such as the end-user’s prior messages and the model/system prompts; the runtime path is via the investigation workflow that ingests those log contents into the troubleshooting LLM context.
W012: Unverifiable external dependency detected (runtime URL that controls agent).
What this means
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
Why it was flagged
The skill explicitly instructs at runtime to load and summarize the Copilot Issues wiki (https://github.com/microsoft/vscode/wiki/Copilot-Issues), which means external content would be fetched and used to directly shape the agent's response.
- Repository
- posit-dev/positron
- Commit
b87c504
- Audited
- Security analysis
Is this your skill?
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.