Escalation Ticket Summary

microsoft/escalation-ticket-summary

Generates a concise IT support ticket summary after troubleshooting paths have been exhausted.

291 tokens

context cost

the whole folder, loaded on every use

files

instructions only

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

npx skills add https://github.com/microsoft/agent-academy --skill escalation-ticket-summary

4 sections, as written by the author

When 2–3 troubleshooting paths have been attempted without success, generate a ticket summary for the employee to submit to the IT support team.

Produce the summary in this structure:

Employee: [Name or 'Not provided']
Date: [Today's date]
Affected Device/Application: [Device type, OS, or application name and version if known]
Symptom/Issue: [Clear description of what is happening]
Error Messages: [Exact error messages seen, if any; 'None reported' if none]
Troubleshooting Steps Already Attempted:
[Step 1]
[Step 2]
[Step 3, if applicable]
Current Status: Unresolved after the above steps.

Fill in each field based on the conversation so far.
Keep descriptions factual and concise.
After presenting the summary, advise the employee to submit it to the IT support team and provide any available escalation contact or ticketing link from the knowledge sources.

Copy the folder

Take microsoft/escalation-ticket-summary 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.