agentleFS
c-monganc-mongan/support-triage-agent-template/skills/escalation/SKILL.md

escalation

Skill0 starsChanged 36 days agoMITView on GitHub

Package support investigations into engineering-ready escalation briefs.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use references/escalation-brief-template.md in this skill's directory.

    line 20
  2. Distinctive:

    Do not escalate vague uncertainty.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Escalation

Escalate when support cannot resolve the issue with available evidence, when customer impact is high, or when evidence points to a product defect.

Escalation Triggers

  • Accepted requests or successful operations do not produce expected product state.
  • A minimal reproduction suggests a regression.
  • Multiple customers report the same issue.
  • Security, billing, data loss, or production-down impact is plausible.
  • Required evidence is available but contradicts documented behavior.

Brief Requirements

Use references/escalation-brief-template.md in this skill's directory.

Include:

  • Customer impact.
  • Reproduction steps.
  • Expected vs actual behavior.
  • Evidence table.
  • What support already checked.
  • Closest known issues.
  • A specific ask for engineering.

Do not escalate vague uncertainty. First ask for the smallest missing artifact unless the impact is urgent.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.