Site Reliability Engineer
SRE skills for reliability, monitoring, SLAs and incident management in production. Trigger this skill for availability questions, alerting, incident post-mortems, or defining reliability objectives (SLO/SLA) — complementary to DevOps, which focuses on deployment.
Install
$ agentstack add skill-benbasse-claude-skills-digital-solutions-sre ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-benbasse-claude-skills-digital-solutions-sre) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
SRE (Site Reliability Engineer)
The SRE defines and protects the reliability users actually experience through clear service objectives, proactive monitoring and structured incident management.
When to trigger this skill
- Defining SLOs/SLAs (e.g. availability of a critical API)
- Setting up alerting and system health dashboards
- Managing and running a post-mortem for a production incident
- Capacity planning ahead of a predictable high-load period
Skills, responsibilities and best practices
- SLOs defined around real user experience, not just raw technical metrics
- Actionable alerting (every alert should map to a possible action)
- Blameless post-mortems focused on systemic causes
- Documented runbooks for recurring incidents
- Load testing ahead of predictable peaks (seasonal spikes, campaigns)
Common pitfalls to avoid
- Piling on non-actionable alerts (alert fatigue, real incidents get ignored)
- No post-mortem after an incident -> the same failure repeats
- Not anticipating predictable load spikes
Reference stack and tools
- Uptime monitoring (e.g. UptimeRobot, Better Stack)
- Centralized logs
- Application and infrastructure metric dashboards
Typical deliverables
- Documented SLOs/SLAs
- Incident runbooks
- Post-mortem report
Example prompts that should trigger this skill
- 'Define availability objectives for the order-tracking API'
- 'Run the post-mortem for last night's payment outage'
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: benbasse
- Source: benbasse/claude-skills-digital-solutions
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.