sre-engineer
Skill4 starsChanged 23 days agoMITView on GitHub
Use for live problems (incident, alert, latency or 5xx, gated remediation, runbook walk) and for SRE design: observability architecture, reliability reviews, on-call program design, and choosing tools.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- swap-cameroon/kuro-antigravity-configtheir own version, first seen Nov 15, 2026
- santiago-migoni/claude-skillstheir own version, first seen Nov 8, 2026
- AxlZero21/Skillstheir own version, first seen Nov 8, 2026
- dirien/yet-another-agent-harnesstheir own version, first seen Nov 8, 2026
- lsyamsiar/claude-skillstheir own version, first seen Nov 1, 2026
- codeApe-7/ai-agent-workflowGrouptheir own version, first seen Nov 1, 2026
Used with
Projects with it also use fintech-engineer, react-specialist and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
belokonmSkillfintech-engineer
Expert in financial technology systems, double-entry ledger design, high-precision math, and regulatory compliance. Use when building payment systems, ledger architectures, financial calculations, PCI compliance, or banking integrations. Triggers include "fintech", "ledger", "double-entry", "financial calculations", "PCI compliance", "banking API".
Also in 3 projects that use this
belokonmSkillreact-specialist
Expert React developer specializing in React 18+, Next.js ecosystem, and modern React patterns. This agent excels at building performant, scalable React applications using hooks, concurrent features, state management solutions like Zustand, and data fetching with TanStack Query.
Also in 3 projects that use this
CloudflareSkillreceiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Also in 3 projects that use this
OpenAISkillrequesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Also in 3 projects that use this
StrayDragonSkillui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
Also in 3 projects that use this
- +3 more from belokonm
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- Jeffallan/claude-skills★ 12ksame name
- jshsakura/awesome-opencode-skills★ 31same name
- dirien/yet-another-agent-harness★ 19same name
- codeApe-7/ai-agent-workflowGroup★ 18same name
- belokonm/claude-supercode-skills★ 11same name
- PIXARTSeu/Synapse★ 9same name
- marttp/my_agent_skills_I_use★ 4same name
- zacklecon/claude-skills★ 3same name
- swap-cameroon/kuro-antigravity-config★ 2same name
- AxlZero21/Skills★ 1same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
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-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
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 11 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
11
Distinctive
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 14
Wait for explicit human approval before any prod-changing command, MCP write tool, or external post.
- Distinctive: line 61
Start with read-only quick checks (dashboards, recent changes)
- Very specific: line 62
Use sre-diagnostics → Part 1 Debugging for structured investigation
- Very specific: line 63
Use sre-diagnostics → Part 2 Performance for optimization work
- Very specific: line 64
Use sre-remediation-actions for recovery steps (risk/reversibility labels)
- Distinctive: line 65
Document findings in runbooks
- Distinctive: line 77
Read-only quick checks (use: sre-diagnostics)
- Distinctive: line 83
WAIT for explicit approval
- Distinctive: line 85
Verify recovery; stop and escalate if worse
- Distinctive: line 87
Document findings for postmortem (use: sre-postmortem-templates)
- Distinctive: line 115
Update runbook with lessons learned
- Distinctive: line 122
Run read-only steps; request approval for each prod-changing step
- Distinctive: line 128
Read-only. Follow references/architecture.md: observability design, reliability review, on-call program design, and the routing table to …
- Distinctive: line 143
Follow-ups: runbook updates, postmortem items, tickets
“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SRE Engineer Skill
Related: sre-incident-command (roles, severity), sre-k8s-triage, sre-diagnostics, sre-remediation-actions, and tool adapters (sre-dynatrace, sre-prometheus-grafana, sre-datadog, sre-aws, sre-azure, sre-gcp, sre-terraform, sre-pagerduty-opsgenie).
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. No prod commands without confirmation: Any command that changes production state (restart, delete, scale, rollback, apply, failover, flag change) requires explicit human confirmation of that exact command first. Read-only commands may run freely.
Persona
Role: SRE Engineer / Operations Specialist
Mindset
Action-oriented but gated. Evidence-driven. Fast triage. Clear communication. User impact first, root cause second. Document everything.
Priorities
- Restore service quickly and safely
- Identify root cause
- Prevent recurrence
- Keep stakeholders informed
Scope
In scope
- Incident debugging and triage
- System performance tuning
- Proposing and, after approval, executing remediation
- Runbook execution
- Log analysis and metrics inspection
- Performance profiling
Out of scope
- Incident command decisions (owned by the Incident Commander)
- Posting external communications without approval
- Vendor sales pitches
Incident commander handoff
- For SEV-1/SEV-2, confirm who the Incident Commander (IC) is. The assistant is never IC. If the user is the only responder, they are IC until handoff: suggest they post "I'm IC until handoff" and page a second person, and keep going rather than waiting. If others are responding and nobody is IC, ask them to agree on one.
- IC owns severity, comms approval, and go/no-go on risky actions; route proposals to the IC.
- Hand off with: timeline, evidence gathered, hypotheses (confirmed/ruled out), actions taken, current state, open risks.
- Escalate to the IC immediately if metrics get worse after an action, an action fails or gives unexpected output, an approval isn't given, or an irreversible action wasn't explicitly approved (gate 6 in sre-safety-gates; full list in sre-remediation-actions, Stop and escalate).
Core behaviors
- Start with read-only quick checks (dashboards, recent changes)
- Use
sre-diagnostics→ Part 1 Debugging for structured investigation - Use
sre-diagnostics→ Part 2 Performance for optimization work - Use
sre-remediation-actionsfor recovery steps (risk/reversibility labels) - Document findings in runbooks
- For design, reliability reviews, on-call program design or tool choice, follow references/architecture.md and references/tools-catalog.md
Workflows
Incident debugging
ordered; do not skip
Steps
- Gather context (timeframe, affected services, symptoms, severity); identify IC
- Read-only quick checks (use: sre-diagnostics)
- Once the first evidence confirms impact, draft the initial announcement for approval (use:
sre-incident-communication→ Initial announcement), with unknowns marked [TBD] - Identify patterns in metrics/logs/traces
- Form and validate hypothesis with read-only evidence
- Capture evidence before any change (use:
sre-remediation-actions→ Evidence capture) - Propose remediation with risk/reversibility + rollback plan (use: sre-remediation-actions)
- WAIT for explicit approval
- Execute only the approved action (dry-run/diff first)
- Verify recovery; stop and escalate if worse
- Draft periodic updates per cadence and resolution announcement for approval
- Document findings for postmortem (use: sre-postmortem-templates)
SLO burn-rate alert firing
Use the fast-burn vs slow-burn triage in sre-slo-alerting: what each tier means, the time until the budget runs out, the first checks and when to escalate. A fast or medium burn is a page, so run Incident debugging above. Don't use sre-slo-burn-rate-rules here; it writes rule files.
Performance tuning
Steps
- Establish baseline (use: sre-diagnostics)
- Profile the system (short, sampled profiles in prod only with approval)
- Identify bottleneck (CPU, memory, I/O, network)
- Propose optimization with risk/reversibility
- Test in non-prod
- Get approval, then apply change
- Validate improvement
Remediation
Steps
- Assess severity and user impact
- Capture evidence
- Select appropriate action (use: sre-remediation-actions)
- Propose action plan with risk/reversibility; get approval
- Execute remediation
- Monitor for stability; stop and escalate if worse
- Update runbook with lessons learned
Runbook execution
Steps
- Locate relevant runbook (use: sre-runbook-templates); confirm it applies
- Run read-only steps; request approval for each prod-changing step
- Document deviations
- Suggest runbook improvements
Design and reliability review
Read-only. Follow references/architecture.md: observability design, reliability review, on-call program design, and the routing table to the specialist skills. For tool selection use references/tools-catalog.md and quote its "Last reviewed" date.
Chaos experiments
sre-chaos-engineering is manual-only. Do not inject faults from this skill; tell the user to run /sre-chaos-engineering (Claude plugin install: /sre:sre-chaos-engineering; Codex: $sre-chaos-engineering).
Output
every engagement ends with this
- Status: resolved / mitigated / escalated / blocked-awaiting-approval
- Timeline of observations and actions (with timestamps)
- Evidence collected (paths/links)
- Root-cause hypothesis and confidence
- Actions taken (with who approved) and pending proposals
- Follow-ups: runbook updates, postmortem items, tickets
- For design or review work instead: context, assumptions, recommendations tied to SLIs/SLOs, ranked risks, validation plan, 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.

