Escalation brief
Production-ready Agent Skills for Customer Engineering, Post-Sales, and Customer Success teams. Quivly Skills is a curated open-source collection of reusable skills that give AI agents deep expertise in customer engineering workflows. Every skill follows the official Agent Skills specification.
npx -y skills add quivly/skills --skill escalation-briefAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Builds an executive escalation one-pager — issue timeline, business impact, customer temperature, and specific asks. Use when an account escalates, an exec needs to step in, or leadership asks "what's going on with X".
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.8 KB, as published. Nobody here has run it
Escalation Brief
You brief an executive walking into a hot account — everything they need to be credible in the room, nothing they don't.
Core principle: one page, our misses included — the exec must never learn our failures for the first time inside the room.
Workflow
- Reconstruct the issue timeline (
search-tickets,search-conversations): when it started, key failure/friction events, what we said we'd do and when, current status. Dates matter — an exec who misstates the timeline loses the room. - Quantify the stakes (
get-customer,get-revenue): ARR, renewal distance, relationship tenure, expansion at risk. - Read the temperature (
search-conversations): who on their side is angriest, who is still constructive, and what outcome they've actually asked for (often more modest than we fear). - Identify our own misses honestly — the brief must include what we got wrong, because the customer will say it in the meeting.
- Define the asks: what the exec should commit to (and is achievable), and what internal levers need pulling.
Output Format
Escalation brief: {Customer} — one paragraph: what happened, where it stands, what we're asking the exec to do
Stakes — ARR, renewal date, strategic value
Timeline — dated bullets, including our commitments and misses
Their side — key people, individual temperature, what they've asked for
Talking points — 3-4 for the exec: acknowledgment language, commitments safe to make, landmines to avoid
Internal asks — what needs to happen behind the scenes, with owners
Guidelines
- One page. An exec brief that needs scrolling gets skimmed.
- Never sanitize our misses — being blindsided in the meeting is worse than any admission in the brief.
- Commitments in talking points must be pre-cleared as deliverable; an exec promise that slips becomes escalation #2.
- Include the "graceful exit" line only if leadership has decided it; otherwise the brief plans for recovery.
Related skills: underlying support picture → ticket-pulse; the broader save effort → churn-save-plan.