troubleshootlisted

<!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. --> # Troubleshoot ## Purpose This skill investigates and explains unexpected agent behavior in the **current Copilot CLI agent session** using its on-disk event log. Use this skill for questions like: - Why did this request take so long? - Why was a tool called (or not called)? - Why did an instruction/skill/agent file not load? - Why did a tool call fail? - Why did the model not follow expectations? Base every conclusion on evidence from the event log. Do not guess. ## Locating the Session Log The skill runs **inside** the session's agent, so the log is on the same machine. It lives outside the workspace — read it via the terminal (`run_in_terminal`), never `grep_search`. 1. **If a `Session log:` path is provided with this message, use it.** It may point to a session **other than** the current one (via `#session`) and may be **comma-separated paths** — investigate all of them and compare. 2. **Sticky reference:** if no path is on the *current* message but an earlier turn in **this conversation** already established a target (a `Session log:` path, or a `#session:` reference), keep analyzing **that same session** for the follow-up. Do **not** fall back to self-discovery here — the newest log is the *current* session, which is the wrong one. Switch only if the user references a new session. 3. **Otherwise, self-discover it:** pick the **most recently