Install any skill in seconds. Free to start, no credit card required.
Get Started Free →pnp/escalate-issue-to-line-manager
Reports important information or incidents to your line manager via email or Teams.
Passed 9 of 17 test cases with the skill, and 5 of 17 without it.
and 3 more in the full report
6 fixed5 passed either way10 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
My manager sent me an email asking 'Did the deploy finish?'. I want to reply directly to that email thread saying 'Yes, deployed successfully at 2 PM'.
| Checked | Without skill | With skill |
|---|---|---|
| Does not invoke an issue escalation workflow. | Passed | Passed |
| Replies directly within the existing email thread. | Missed | Passed |
The instructions your model reads when the skill loads.
Quickly notify your line manager of an issue, incident, or important update — delivered as an email or Teams message, with an optional coordination chat.
Resolve the manager. Call GetManagerDetails to get name and email. If
no manager is configured, stop and tell the user.
Gather context with one combined question. Use AskUserQuestion to ask:
If referencing existing content, retrieve it first: GetMessage for an
email, GetChatMessage for a Teams message. Quote the relevant excerpt in
the body.
Draft the message using this template:
[CRITICAL] | [IMPORTANT] | [FYI] — <topic>
(only Critical and Important get a bracketed prefix; Notify uses plain subject)Preview and confirm before sending. Show the full drafted subject and body. Ask: "Send this now, or change anything?" Do NOT send Critical or Important messages without explicit confirmation. Notify-level may send directly if the user has already approved the draft.
Send:
SendEmailWithAttachments to manager (CC any extra recipients).test cases passed, vs 5 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.