monitoring SKILL.md skillA
monitoring from ericrisco/rsc-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ericrisco/rsc-harness/monitoring@git:20260729.111532cPins git:20260729.111532c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ericrisco/rsc-harness
- Path
skills/monitoring/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260729.111532c, committed Jul 29, 2026
- First version recorded
- Jun 2, 2026
- Size
- 12,302 bytes
- Repository stars
- 236
- License
- MIT
Use when setting up uptime and health monitoring, alerts, or on-call basics for a service already in production, so you learn it is down before customers do — health and readiness probes, alerting on SLO error-budget burn rather than raw counts, curing alert fatigue, on-call rotation with escalation, and a status page. NOT instrumenting logs, metrics or traces, or wiring OpenTelemetry (that is `observability`).
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 You are wiring up the *outside* view of a service that already shipped: is it alive, is it fast, and when it breaks, does exactly one human get exactly one actionable page. This skill emits a concrete setup — a checker config, a health-endpoint contract, symptom-based alert rules, and an on-call rotation. Not telemetry instrumentation (that is `../observability/SKILL.md`), not the release-gating healthcheck (that is `../deployment/SKILL.md`). ## The one rule **A page is justified only when there is real user impact AND a human action the system can't take itself.** Everything below descends from this. Internalize the three tiers: - **Page** (wake someone): users are hurting now and a human must intervene. Checkout returns 5xx. Site unreachable. Error budget burning fast. - **Ticket** (look during business hours): degraded but not bleeding. Slow-burn budget use, cert expiring in 14 days. - **Dashboard-only** (don't notify): CPU at 80%, a single retry, a transient blip the system already healed. If an alert doesn't map to an immediate human action, it is not a page — it's noise, and noise trains people to ignore the one page that matters. ## The 4-layer stack …
Read the whole file at its exact version.
How to install
mdr add ericrisco/rsc-harness/monitoring@sha256:2e27a75f7218c240The line at the top of this page pins the label git:20260729.111532c, 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_jlxjo65jgdefdho2)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 2, 2026 and Jul 29, 2026, about one every 57 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260729.111532c latest | 2026-07-29 | 111532c | 12,302 B | A | view · diff |
| git:20260602.004e38d | 2026-06-02 | 004e38d | 12,581 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 (12302 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
ericrisco/rsc-harness · 236 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jlxjo65jgdefdho2 GET https://markdownregistry.com/api/v1/resolve?ref=ericrisco/rsc-harness/monitoring GET https://markdownregistry.com/api/v1/blob/2e27a75f7218c240c07ae95c2b5331f07df5f118f755c8d727ac38200319b3d5
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.
More from ericrisco/rsc-harness
Every file in ericrisco/rsc-harness