Better Stack On-Call skillA
Better Stack On-Call is agent-read markdown (skill) from wyre-ai/msp-claude-plugins: Better Stack on-call: on-call calendars and rotations, escalation and notification policies, alert routing, and determining who is currently on call..
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 On-Call Management ## Overview Better Stack Uptime includes integrated on-call scheduling that determines who gets paged when a monitor fails. Schedules define rotation patterns, and notification/escalation policies define how and when responders are alerted (via phone, SMS, email, or push). For MSPs, on-call is commonly configured per customer team, with separate schedules for each client's SLA requirements. ## Anti-triggers - **Rotations that live in PagerDuty or Rootly** — "who is on call", "escalation policy", and "paging" are shared vocabulary across all three products, and nothing in the phrasing disambiguates them. If the MSP's paging system is not Better Stack, use `pagerduty-oncall` or `rootly-oncall`. - **Technician shifts, dispatch, or booked appointments** — an on-call rotation is not a service schedule; that lives in the PSA (`autotask`, `halopsa`, `connectwise-psa`). - **Changing what a monitor checks rather than who it wakes** — use `betterstack-monitors`. ## Key Concepts ### Schedule Structure Better Stack schedules define: - **Members** - Responders in the rotation - **Rotation** - Daily, weekly, or custom patterns …
Read the whole file at its exact version.
How to install
mdr add wyre-ai/msp-claude-plugins/Better Stack On-Call@git:20260804.055e86emdr add wyre-ai/msp-claude-plugins/Better Stack On-Call@sha256:697613535295c085Pin 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_wjjdpc4cywbp6ifv)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260804.055e86e latest | 2026-08-04 | 055e86e | 6,767 B | A | view · diff |
| git:20260728.b7e78fc | 2026-07-28 | b7e78fc | 6,172 B | A | view · diff |
| git:20260713.1fbd3f3 | 2026-07-13 | 1fbd3f3 | 6,297 B | A | view · diff |
| git:20260405.09d00fc | 2026-04-05 | 09d00fc | 6,318 B | A | view · diff |
| git:20260327.99a903e | 2026-03-27 | 99a903e | 6,125 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 (6767 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_wjjdpc4cywbp6ifv GET https://markdownregistry.com/api/v1/resolve?ref=wyre-ai/msp-claude-plugins/Better Stack On-Call GET https://markdownregistry.com/api/v1/blob/697613535295c085e6347deadafca1c8b025435bdef828cca05781063f9a901a
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.