monitoring-conventions SKILL.md skillA
monitoring-conventions from msolecki/developer-os is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add msolecki/developer-os/monitoring-conventions@git:20261024.8456bc0Pins git:20261024.8456bc0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- msolecki/developer-os
- Path
plugin/skills/monitoring-conventions/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261024.8456bc0, committed Oct 24, 2026
- First version recorded
- Oct 14, 2026
- Size
- 1,106 bytes
- Repository stars
- 3
- License
- MIT
Alert on symptoms, prevent alert fatigue, link runbooks, and separate health from readiness checks. Use when editing infrastructure code (CDK, Terraform, serverless config, CI workflows) or adding metrics and alerts.
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 rules - Alert on SYMPTOMS such as error rate above 1%, p99 above 2 seconds, or a growing queue; do not page on causes such as CPU above 80% or memory use. Causes belong on dashboards. - Prevent alert fatigue. If an alert fires three times without action, tune its threshold or remove it. An ignored alert is worse than no alert. - Every paging alert links to a runbook that says what to inspect, what to restart, and whom to escalate to. Do not add an alert without a runbook. - Separate `/health` for process liveness and load balancers from `/ready` for dependency readiness and orchestration. A health check does not query the database. - Add a new metric or alert in the same change as the feature it observes. Do not defer monitoring to an unspecified later task.
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_oieyylva2qxvjzqo/1f3e52e45e74973f01a41d58aea250f2ca4eb3cd103814baecddd0aed89c9d69.json
Then /plugin install monitoring-conventions@markdownregistry-oieyylva2qxvjzqo in Claude Code. It installs git:20261024.8456bc0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add msolecki/developer-os/monitoring-conventions@sha256:1f3e52e45e74973fThe line at the top of this page pins the label git:20261024.8456bc0, 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_oieyylva2qxvjzqo)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in msolecki/developer-os/monitoring-conventions since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of monitoring-conventions from somewhere else? Ask it: where did my monitoring-conventions come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Oct 14, 2026 and Oct 24, 2026, about one every 3 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261024.8456bc0 latest | 2026-10-24 | 8456bc0 | 1,106 B | A | view · diff |
| git:20261015.933b000 | 2026-10-15 | 933b000 | 1,142 B | A | view · diff |
| git:20261015.eeda64b | 2026-10-15 | eeda64b | 1,138 B | A | view · diff |
| git:20261014.c8129da | 2026-10-14 | c8129da | 1,060 B | A | view · diff |
| git:20261014.53504f8 | 2026-10-14 | 53504f8 | 1,078 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/monitoring-conventions/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (1106 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
msolecki/developer-os · 3 stars · license MIT · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_oieyylva2qxvjzqo GET https://markdownregistry.com/api/v1/resolve?ref=msolecki/developer-os/monitoring-conventions GET https://markdownregistry.com/api/v1/blob/1f3e52e45e74973f01a41d58aea250f2ca4eb3cd103814baecddd0aed89c9d69
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.