Devops Sre Practices

Use when the user asks about SRE practices, starting an SRE program, toil reduction, production readiness reviews, reliability maturity, SLOs and an error budget policy across many services, or blameless postmortem culture. Produces an SRE operating model and adoption plan. Not for SLI math and burn-rate alerts (use sre-sli-slo-management) or incident process (use devops-incident-response).

45 stars 6 forksDevOps & Cloud

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add j4flmao/agent-skills --skill devops-sre-practices
Manual install
git clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/devops/sre-practices ~/.claude/skills/devops-sre-practices

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# SRE Practices

## Purpose
Implement Site Reliability Engineering practices: define SLIs/SLOs aligned with business goals, manage error budgets with burn rate alerts, systematically reduce toil, conduct blameless incident analysis, build production readiness reviews, and mature reliability culture across the organization.

## Agent Protocol

### Trigger
Exact user phrases: "SRE", "site reliability", "SLI", "SLO", "error budget", "error budget policy", "burn rate", "toil", "toil reduction", "reliability engineering", "postmortem", "incident analysis", "5 whys", "production readiness review", "PRR", "reliability dashboard", "multi-window", "multi-burn-rate", "reliability maturity", "SLO monitoring", "service level objective", "service level indicator".

### Input Context
- Current monitoring and alerting stack (Prometheus, Datadog, Grafana)
- Existing incident response process
- Team size and on-call rotation structure
- Current service-level objectives (if any)
- Known reliability pain points and past incidents
- Business context (revenue-critical services vs internal tools)

### Output Artifact
SLI/SLO definition document, error budget policy, burn rate alert rules, toil assessment with reduction plan, postmortem template, production readiness checklist, and reliability dashboard configuration.

### Response Format
Prometheus recording rules, Grafana dashboard JSON, markdown documents, and YAML alert rules. No preamble. No postamble. No filler.

### Completion Criteria
Read the full skill on GitHub

Details

Skill name
devops-sre-practices
Path
skills/devops/sre-practices/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Devops Sre Practices skill do?

Use when the user asks about SRE practices, starting an SRE program, toil reduction, production readiness reviews, reliability maturity, SLOs and an error budget policy across many services, or blameless postmortem culture. Produces an SRE operating model and adoption plan. Not for SLI math and burn-rate alerts (use sre-sli-slo-management) or incident process (use devops-incident-response).

How do I install the Devops Sre Practices skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill devops-sre-practices. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Devops Sre Practices popular?

It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.

Related skills

Agent Observability

45

j4flmao/agent-skills

Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).

DevOps & Cloud

AI Agent Architectures

45

j4flmao/agent-skills

Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).

AI, LLMs & Agents

AI Agent Core Loop

45

j4flmao/agent-skills

Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).

AI, LLMs & Agents

Digitalocean

45

j4flmao/agent-skills

Use when the user asks about DigitalOcean, Droplets, DOKS, App Platform, Spaces, managed databases, reserved IPs, cloud firewalls, doctl, or the Terraform digitalocean provider. Produces DigitalOcean infrastructure and IaC. Not for AWS (use aws) or Hetzner (use hetzner-cloud).

DevOps & Cloud

Devops Service Mesh

45

j4flmao/agent-skills

Use when the user asks about service mesh, Istio, Istio ambient mode, Linkerd, Envoy sidecars, mTLS between services, VirtualService and DestinationRule, mesh retries and timeouts, or mesh observability. Produces mesh install, traffic and security policies. Not for Cilium networking (use cilium-ebpf) or Consul (use consul).

DevOps & Cloud

Docker Internals

45

j4flmao/agent-skills

Use when the user asks how containers work, Linux namespaces and cgroups v2, OverlayFS layers and copy-on-write, containerd and runc, the OCI runtime spec, container PID 1 and signals, or why a container is OOM killed. Explains container primitives for debugging and hardening. Not for Dockerfile authoring (use docker-patterns) or image scanning (use security-container-security).

DevOps & Cloud

Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.