sre-production-readiness
Skill4 starsChanged 25 days agoMITView on GitHub
Use before a new service or major change goes live: run a production readiness review (PRR) / launch checklist and produce a pass/fail verdict with evidence.
In this repository84 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/sre-safety-gates.mdcCursor rule
- sre-awsSkill
- sre-azureSkill
- sre-capacity-planningSkill
- sre-change-safetySkill
- sre-chaos-engineeringSkill
- sre-cloud-cost-reviewSkill
- sre-database-triageSkill
- sre-datadogSkill
- sre-dependency-mappingSkill
- sre-diagnosticsSkill
- sre-dr-backup-testSkill
- sre-dynatraceSkill
- sre-emudhra-ca-checkSkill
- sre-engineerSkill
- sre-expiry-auditSkill
- sre-gcpSkill
- sre-incident-commandSkill
- sre-incident-communicationSkill
- sre-k8s-safe-remediationSkill
- sre-k8s-triageSkill
- sre-k8s-upgrade-autopilotSkill
- sre-message-queue-triageSkill
- sre-migration-safetySkill
- sre-observability-cost-cutterSkill
- sre-observability-query-cookbookSkill
- sre-oncall-auditSkill
- sre-oncall-handoffSkill
- sre-pagerduty-opsgenieSkill
- sre-php2shell-checkSkill
- sre-postmortem-templatesSkill
- sre-prometheus-grafanaSkill
- sre-remediation-actionsSkill
- sre-runbook-templatesSkill
- sre-safety-gatesSkill
- sre-security-incident-triageSkill
- sre-service-mesh-triageSkill
- sre-slo-alertingSkill
- sre-slo-burn-rate-rulesSkill
- sre-terraformSkill
- sre-toil-reviewSkill
- sre-awsSkill
- sre-azureSkill
- sre-capacity-planningSkill
- sre-change-safetySkill
- sre-chaos-engineeringSkill
- sre-cloud-cost-reviewSkill
- sre-database-triageSkill
- sre-datadogSkill
- sre-dependency-mappingSkill
- sre-diagnosticsSkill
- sre-dr-backup-testSkill
- sre-dynatraceSkill
- sre-emudhra-ca-checkSkill
- sre-engineerSkill
- sre-expiry-auditSkill
- sre-gcpSkill
- sre-incident-commandSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Wait for explicit human approval before any prod-changing command, MCP write tool, or external post.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SRE Production Readiness Review (PRR)
Safety gates (REQUIRED)
- Read-only diagnosis first.
- Propose each change with risk (low/med/high) and reversibility.
- Wait for explicit human approval before any prod-changing command, MCP write tool, or external post.
- Act only as approved, verify, and stop and escalate if anything gets worse.
Full rules: sre-safety-gates. Read-only MCP setup: sre-safety-gates/references/mcp.md.
Comprehensive checklist and template for ensuring services are ready for production-grade traffic and on-call support.
PRR checklist
Observability
- Are the Four Golden Signals (Latency, Errors, Traffic, Saturation) monitored?
- Is there a dashboard for this service in the central monitoring system?
- Are SLOs defined and agreed upon by stakeholders?
- Does the service have distributed tracing (OpenTelemetry) implemented?
Alerting
- Are alerts symptom-based rather than cause-based?
- Is there a runbook for every alert that can page a human?
- Are alert routing and escalation paths verified?
Reliability
- Has the service been load tested to 2x expected peak?
- Is there a graceful degradation/failover plan for all dependencies?
- Has a Chaos experiment (e.g., Pod Kill) been performed in staging?
- Is the service deployed across at least two Availability Zones?
Operations
- Is there an automated rollback mechanism?
- Is the service configuration version-controlled and auditable?
- Is there a documented process for database migrations?
- Has an on-call rotation been established and staffed?
PRR document template
# Production Readiness Review: [Service Name]
**Status:** [Draft / Under Review / Approved]
**Owner:** [Team Name]
## 1. Service Overview
Brief description of the service and its criticality.
## 2. Dependency Map
- **Upstream:** [What calls this?]
- **Downstream:** [What does this call?]
- **Criticality:** [What happens if this service fails?]
## 3. Observability & SLOs
- **SLO Link:** [Link to sre-slo-alerting output]
- **Dashboard Link:** [URL]
## 4. Scaling & Capacity
- **Current Capacity:** [e.g., 5k RPS]
- **Scaling Trigger:** [e.g., CPU > 60%]
## 5. Security & Compliance
- [ ] Secret management (Vault/Secrets Manager)
- [ ] TLS enabled for all traffic, certs not chained through a known-compromised CA (`sre-expiry-audit` for expiry, `sre-emudhra-ca-check` for the Oct 2026 eMudhra compromise)
- [ ] Vulnerability scanning passed (check language/framework runtimes against open CVEs too, e.g. `sre-php2shell-check` for PHP)
## 6. Approval Sign-off
- **SRE Lead:** ___________
- **Engineering Manager:** ___________Output
- PRR report: each checklist item marked pass / fail / n.a. with evidence; overall verdict ready / ready-with-risks / not-ready; blocking items with owners
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

