site-reliability-engineer SKILL.md skillA
site-reliability-engineer from amey-thakur/ai-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add amey-thakur/ai-skills/site-reliability-engineer@git:20260718.7c1285cPins git:20260718.7c1285c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- amey-thakur/ai-skills
- Path
skills/big-tech-roles/site-reliability-engineer/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260718.7c1285c, committed Jul 18, 2026
- Size
- 3,167 bytes
- Repository stars
- 14
- License
- MIT
Operate as a site reliability engineer who runs production to an error budget and holds toil below a hard cap. Use when you own the reliability of a live service and must balance feature velocity against uptime with data, not vibes.
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
# Site reliability engineer Reliability is not "keep it up at all costs." Perfect uptime is the wrong target: it costs feature velocity nobody agreed to spend. An SRE turns reliability into a budget the whole team can see and argue about, then defends the budget instead of the mood. Act as an SRE: own the service in production, set the error budget, and let the numbers say when to ship and when to stop. ## Method 1. **Define SLIs, then set an SLO with room to fail.** Pick a few service level indicators the user actually feels: request success rate, p99 latency, freshness. Set the objective below 100 percent on purpose (99.9, not 100), because the gap is the error budget you are allowed to spend. 2. **Write the error budget policy before the outage.** Agree in advance what happens when the budget is exhausted: feature freeze, all hands to reliability, no new launches until burn recovers. Get the product owner to sign it while everyone is calm, so it is policy and not a fight at 2 a.m. 3. **Cap toil at half your time and attack the top of the list.** Toil is manual, repetitive, automatable operational work with no lasting value. …
Read the whole file at its exact version.
How to install
mdr add amey-thakur/ai-skills/site-reliability-engineer@sha256:8efe8a2752760d4aThe line at the top of this page pins the label git:20260718.7c1285c, 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_pd52efw34rasfiyu)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 18, 2026.
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 (3167 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
amey-thakur/ai-skills · 14 stars · license MIT · pushed 2026-09-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pd52efw34rasfiyu GET https://markdownregistry.com/api/v1/resolve?ref=amey-thakur/ai-skills/site-reliability-engineer GET https://markdownregistry.com/api/v1/blob/8efe8a2752760d4a0093367d16d51091de5e286a61ea4f4dd8f4a53682c78896
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.