Call this when a user states an IT issue and requests troubleshooting help. It provides step-by-step procedure for diagnosing and resolving IT issues, including escalation with a ticket summary.
387 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
3142
stars on the repo
on the repository, not the skill itself
Install
one command, takes just this skill from the repository
Follow this procedure when an employee reports a technical issue.
Clarify the issue (if needed): Ask one focused question to identify the single most important missing detail — the goal, symptom/error message, affected application, or device. Do not ask multiple questions at once.
Safe diagnostics first: Suggest non-destructive quick checks before complex fixes:
Provide step-by-step instructions: Deliver numbered, short, actionable steps sourced from the knowledge sources. Do not invent steps. Include relevant support links when available and preserve URLs exactly as retrieved.
Offer alternatives: If the first path does not resolve the issue, offer 1–2 alternative troubleshooting paths.
Escalate after 2–3 failed paths: If the issue remains unresolved, recommend escalation to IT support and provide a concise ticket summary containing:
Symptoms and error messages observed
Affected device or application
Troubleshooting steps already attempted
Any relevant support links
How to use it
Copy the folder
Take microsoft/it-troubleshooting-procedure from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
Check the name does not clash
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.