Skip to content
TrustedSkillsbeta
Back to all skills

Escalation Governance

Checked
athola·vlatest·other·MIT

This skill automates and monitors escalation workflows, ensuring consistent processes & timely resolutions for improved efficiency and compliance.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add athola/claude-night-market --skill escalation-governance -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

athola

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned athola/claude-night-market at 9045831255.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
9045831255
Manifest
plugins/abstract/skills/escalation-governance/SKILL.md
Scanned
5 files, 571 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The escalation-governance skill manages and directs the process of escalating issues or requests to higher levels of authority. It ensures that escalations follow predefined procedures, including documenting reasons for escalation, identifying appropriate recipients, and tracking resolution progress. This promotes accountability and efficient handling of critical situations requiring intervention from senior stakeholders.

When to use it

  • Complex Incident Response: When an incident requires involvement from multiple teams or leadership due to its severity or impact.
  • Policy Exceptions: To formally request and document deviations from established policies, ensuring proper review and approval.
  • Service Level Agreement (SLA) Breaches: When a service is failing to meet agreed-upon performance targets, triggering escalation protocols for investigation and remediation.
  • Unresolved Customer Complaints: When customer issues remain unresolved after standard support channels have been exhausted.

Key capabilities

  • Defines escalation paths based on issue type or severity.
  • Automates notification of relevant stakeholders during escalation.
  • Tracks the status and resolution of escalated items.
  • Provides documentation for escalation reasons and actions taken.

Example prompts

  • "Escalate this incident [incident ID] to Tier 2 support due to ongoing performance degradation."
  • "Initiate a policy exception request for [policy name] regarding [specific situation]."
  • “Create an escalation ticket for customer complaint #12345, noting that the issue remains unresolved after three attempts.”

Tips & gotchas

The skill relies on accurate incident and stakeholder data. Ensure your systems are properly configured with relevant information to avoid misdirected escalations.