monitoring-and-alerting SKILL.md skillA
monitoring-and-alerting from rampstackco/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add rampstackco/claude-skills/monitoring-and-alerting@git:20260810.e5bc675Pins git:20260810.e5bc675 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- rampstackco/claude-skills
- Path
skills/monitoring-and-alerting/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260810.e5bc675, committed Aug 10, 2026
- First version recorded
- Apr 28, 2026
- Size
- 10,455 bytes
- Repository stars
- 1,037
- License
- MIT
Design and run a monitoring system for a website or web app. Use this skill when setting up uptime checks, defining SLOs, configuring error tracking, choosing what to alert on, designing on-call rotations, or fixing alert fatigue. Triggers on monitoring, alerts, uptime, SLO, SLA, error rate, on-call, pager, alert fatigue, observability, dashboards, what should we monitor. Also triggers when an incident reveals a gap in monitoring.
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
# Monitoring and Alerting Decide what to watch, what to alert on, and how to make sure the right person finds out when things break. --- ## When to use - Setting up monitoring on a new site or service - Defining SLOs (service level objectives) and error budgets - Choosing which alerts page someone vs which go to a quiet channel - Designing or fixing on-call rotation - Diagnosing alert fatigue - Filling monitoring gaps revealed by an incident - Migrating monitoring vendors ## When NOT to use - Responding to an active incident (use `incident-response`) - Writing the post-mortem (use `after-action-report`) - Designing analytics dashboards for product metrics (use `analytics-strategy`) - Performance optimization itself (use `performance-optimization`) --- ## Required inputs - The system you're monitoring (URLs, services, dependencies) - Existing monitoring tools (uptime, errors, logs, APM) - Business hours and team timezone(s) - Who is on-call or available for incidents - Existing SLOs or success metrics, if any --- ## The framework: 4 layers Monitoring works in layers. Skip a layer and you'll miss a class of problems. ### Layer 1: Availability …
Read the whole file at its exact version.
How to install
mdr add rampstackco/claude-skills/monitoring-and-alerting@sha256:7f9226b4e7015829The line at the top of this page pins the label git:20260810.e5bc675, 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_otqqxfm74n2rnaus)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 28, 2026 and Aug 10, 2026, about one every 26 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260810.e5bc675 latest | 2026-08-10 | e5bc675 | 10,455 B | A | view · diff |
| git:20260810.b3c37f1 | 2026-08-10 | b3c37f1 | 9,932 B | A | view · diff |
| git:20260507.ac2b078 | 2026-05-07 | ac2b078 | 9,848 B | A | view · diff |
| git:20260505.c80b896 | 2026-05-05 | c80b896 | 9,814 B | A | view · diff |
| git:20260428.f066ffe | 2026-04-28 | f066ffe | 9,697 B | A | 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 (10455 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
rampstackco/claude-skills · 1,037 stars · license MIT · pushed 2026-10-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_otqqxfm74n2rnaus GET https://markdownregistry.com/api/v1/resolve?ref=rampstackco/claude-skills/monitoring-and-alerting GET https://markdownregistry.com/api/v1/blob/7f9226b4e701582962501644364d7516987882c9d06745bb0e2cb417da0d3bcc
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.