Better Stack Incidents skillA
Better Stack Incidents is agent-read markdown (skill) from wyre-ai/msp-claude-plugins: Better Stack incidents: incident records raised by uptime monitors or reported manually, and the triage, acknowledgment, and resolution lifecycle..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Better Stack Incidents ## Overview Incidents in Better Stack are triggered automatically when uptime monitors detect downtime, or created manually for ad-hoc issues. Each incident tracks the timeline from detection through acknowledgment to resolution, with associated monitors, status page updates, and on-call notifications. ## Anti-triggers - **A security incident** — Better Stack incidents are uptime events with no threat model, no indicators, and no remediation flow; use `huntress-incidents`. - **The MSP's major-incident process** — if the question is about incident commanders, customer comms, or postmortems rather than a failing check, use `rootly-incidents` or `pagerduty-incidents`. - **Billable follow-up work** — an incident is not a PSA ticket; use `autotask`, `halopsa`, or `connectwise-psa`. - **Telling end users about the outage** — use `betterstack-status-pages`. ## Key Concepts ### Incident Lifecycle 1. **Triggered** - Monitor detects downtime and creates an incident 2. **Acknowledged** - On-call responder acknowledges the incident 3. **Resolved** - The issue is fixed and the incident is closed …
Read the whole file at its exact version.
How to install
mdr add wyre-ai/msp-claude-plugins/Better Stack Incidents@git:20260804.055e86emdr add wyre-ai/msp-claude-plugins/Better Stack Incidents@sha256:0a64e961122184faPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_pa3itncslja2lyhl)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260804.055e86e latest | 2026-08-04 | 055e86e | 5,840 B | A | view · diff |
| git:20260728.b7e78fc | 2026-07-28 | b7e78fc | 5,259 B | A | view · diff |
| git:20260713.1fbd3f3 | 2026-07-13 | 1fbd3f3 | 5,312 B | A | view · diff |
| git:20260405.09d00fc | 2026-04-05 | 09d00fc | 5,323 B | A | view · diff |
| git:20260327.99a903e | 2026-03-27 | 99a903e | 5,167 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 (5840 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 · 46 stars · license Apache-2.0 · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pa3itncslja2lyhl GET https://markdownregistry.com/api/v1/resolve?ref=wyre-ai/msp-claude-plugins/Better Stack Incidents GET https://markdownregistry.com/api/v1/blob/0a64e961122184fa3a1935f96dbf8743a36c6bcafd2bec6fc8aa13460b124020
Your agent 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.