AB troubleshoot
Investigate unexpected behavior in the current Copilot agent session by analyzing its event log. Use when the user asks why something happened, why a request was slow, why a tool was or was not used, or why instructions/skills/agents did not load.
A skill for diagnosing why your Copilot agent misbehaved. Digs through session event logs to find why something ran slow, a tool didn't trigger, instructions failed to load, or behavior went sideways. No critical errors in the files, linter passed, safety score maxed at 100. Quality at 87 is solid for an analyzer—process score of 68 suggests the logic works but has rough edges.
No model runs, no sandbox testing. The skill passed static checks only. Supports all major platforms: Claude, Cursor, Copilot, and a dozen others. Useful for session debugging if the metrics hold up. Install it, but expect real-world quirks to surface once you run it.
Investigate unexpected behavior in the current Copilot agent session by analyzing its event log.
As a process B 68/100 · Nearly there — weak spots: inputs and preconditions, running it twice
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 68/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 7 mutating operations with no state check
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 85Steps. 65 steps, 1 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3307 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (13 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 247: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 65 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.