SRE-Skills / rules
Cursor rule4 starsChanged 23 days agoMITView on GitHub
SRE pack safety gates (always on)
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,243 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository84 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- 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-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 sre-safety-gates.mdc into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Diagnose read-only first: Use only read commands and read-only MCP tools (get, describe, logs, history, plan, queries, dashboards).
- Very specific: line 13
Act: Run exactly what was approved — nothing more.
- Distinctive: line 15
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 17
Never run a write command, call an MCP write tool, or post an external message without explicit human approval.
≈ “Common” is an estimate: at least 1 in 5 of the 6,809 Cursor rule 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
--- description: SRE pack safety gates (always on) alwaysApply: true --- <!-- GENERATED by scripts/build-targets.py from .claude/skills/*/SKILL.md. Do not edit; edit the skills and re-run. --> # SRE safety gates 1. **Diagnose read-only first.** Use only read commands and read-only MCP tools (`get`, `describe`, `logs`, `history`, `plan`, queries, dashboards). Change nothing. 2. **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. 3. **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. 4. **Act.** Run exactly what was approved — nothing more. Prefer dry-run/diff/plan output first. 5. **Verify.** Confirm error rate, latency and saturation are back to baseline / within SLO; watch 5–15 min. 6. **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. Never run a write command, call an MCP write tool, or post an external message without explicit human approval. Skills live in `.claude/skills/` (Cursor reads them natively); manual-only skills must be started by the user with `/<skill-name>`.
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.

