Huntress Escalations SKILL.md skillA
Huntress Escalations from wyre-ai/msp-claude-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wyre-ai/msp-claude-plugins/Huntress Escalations@git:20260804.8cec48aPins git:20260804.8cec48a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wyre-ai/msp-claude-plugins
- Path
msp-claude-plugins/huntress/huntress/skills/escalations/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260804.8cec48a, committed Aug 4, 2026
- First version recorded
- Feb 26, 2026
- Size
- 4,650 bytes
- Repository stars
- 52
- License
- Apache-2.0
Huntress SOC escalations: how an escalation differs from an incident, escalation priority levels, the list/get/resolve tools, escalation-to-incident correlation, and the already-resolved and not-found error cases.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Huntress Escalations ## Overview Escalations are high-priority notifications from the Huntress SOC to MSP partners. When the Huntress SOC identifies activity requiring partner attention or action, they create an escalation. MSPs must review escalations promptly and resolve them after taking appropriate action. ## Key Concepts ### Escalation vs Incident - **Incidents** are confirmed threats with recommended remediations - **Escalations** are SOC-to-partner communications requiring human review and decision-making - Escalations may be related to incidents but can also cover other situations ### Escalation Priority Escalations from the Huntress SOC indicate urgency. Treat all open escalations as time-sensitive communications requiring prompt review. ## Anti-triggers - **A confirmed threat with a remediation to approve** — that is an incident, a separate object with its own approve/reject flow; an escalation is a message asking a human to decide. Use `huntress-incidents`. - **A detection that no analyst has looked at yet** — pre-triage telemetry never reaches the partner as an escalation; use `huntress-signals`. ## API Patterns ### List Escalations ``` …
Read the whole file at its exact version.
How to install
mdr add wyre-ai/msp-claude-plugins/Huntress Escalations@sha256:f56c6dd161c5ef9eThe line at the top of this page pins the label git:20260804.8cec48a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_4xdpsbfzl2vgk5px)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Feb 26, 2026 and Aug 4, 2026, about one every 40 days. Its first recorded version is graded B and its latest A.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260804.8cec48a latest | 2026-08-04 | 8cec48a | 4,650 B | A | view · diff |
| git:20260728.b7e78fc | 2026-07-28 | b7e78fc | 4,265 B | A | view · diff |
| git:20260713.1fbd3f3 | 2026-07-13 | 1fbd3f3 | 4,187 B | A | view · diff |
| git:20260405.09d00fc | 2026-04-05 | 09d00fc | 4,191 B | A | view · diff |
| git:20260226.004fb80 | 2026-02-26 | 004fb80 | 4,069 B | B | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4650 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wyre-ai/msp-claude-plugins · 52 stars · license Apache-2.0 · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4xdpsbfzl2vgk5px GET https://markdownregistry.com/api/v1/resolve?ref=wyre-ai/msp-claude-plugins/Huntress Escalations GET https://markdownregistry.com/api/v1/blob/f56c6dd161c5ef9ef4f525af491ba158444ff19e9a4d57db87c40d5f31c45397
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.