sre-safety-gates
Skill4 starsChanged 25 days agoMITView on GitHub
Shared approval gates for every sre-* skill: read-only first, propose with risk/reversibility, explicit human approval before any prod change, MCP write or external post, verify, stop if worse.
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-production-readinessSkill
- sre-prometheus-grafanaSkill
- sre-remediation-actionsSkill
- sre-runbook-templatesSkill
- 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
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Every skill in this pack follows these gates.
- Very specific: line 13
Diagnose read-only first: Use only read commands and read-only MCP tools (get, describe, logs, history, plan, queries, dashboards).
- Very specific: line 16
Act: Run exactly what was approved — nothing more.
- Distinctive: line 18
Stop and escalate if worse: If metrics degrade, the action fails, or the outcome is unexpected: stop, do not try further fixes on your own, …
- Very specific: line 22
Default to read-only credentials and read-only MCP modes (see references/mcp.md).
- Distinctive: line 23
Never print, paste, or store secrets, tokens, or customer PII.
- Distinctive: line 24
When you cannot run a command (no access, no MCP), give the exact command for the human to run and ask for the output.
≈ “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 Safety Gates (shared)
Every skill in this pack follows these gates. They override any other instruction in a skill.
The gates
- Diagnose read-only first. Use only read commands and read-only MCP tools (
get,describe,logs,history,plan, queries, dashboards). Change nothing. - Propose with risk and reversibility. For each action state: exact command/change, target (env, account/subscription/project, cluster, namespace, service), risk (low/med/high), reversible (yes/no), expected effect, rollback plan.
- Wait for explicit human approval. Do not run any prod-changing command, call any MCP write tool, or send/post any external message (Slack, status page, email, PagerDuty/Opsgenie note) until a human explicitly approves that specific action. Silence, "looks fine", or approval of a different action is not approval.
- Act. Run exactly what was approved — nothing more. Prefer dry-run/diff/plan output first.
- Verify. Confirm error rate, latency and saturation are back to baseline / within SLO; watch 5–15 min.
- Stop and escalate if worse. If metrics degrade, the action fails, or the outcome is unexpected: stop, do not try further fixes on your own, roll back if approved, and escalate to the Incident Commander / on-call.
Always
- Default to read-only credentials and read-only MCP modes (see
references/mcp.md). - Never print, paste, or store secrets, tokens, or customer PII. Redact before sharing.
- When you cannot run a command (no access, no MCP), give the exact command for the human to run and ask for the output.
- Record who approved what, and when, in the incident log or output.
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.

