sre-engineer

An agent skill by Jeffallan, from Jeffallan/claude-skills. Tags: automation, cloud, devops, performance, priority.

What it does

Defines service level objectives, creates error budget policies, designs incident response procedures, develops capacity models, and produces monitoring configurations and automation scripts for production systems. Use when defining SLIs/SLOs, managing error budgets, building reliable systems at scale, incident management, chaos engineering, toil reduction, or capacity planning.

Install

With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:

npx skills add Jeffallan/claude-skills --skill sre-engineer

Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):

git clone --depth 1 https://github.com/Jeffallan/claude-skills
cp -r claude-skills/skills/sre-engineer ~/.claude/skills/sre-engineer

Safety box score

Grade D, elevated risk: 51 of 100 risk points, rated 2026-10-20. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.

This skill is an SRE/operator toolset that defines SLOs, monitoring, incident response, and automation for live systems. The main risks are broad operational control: it includes scripts and examples that can run shell commands, restart services, delete pods, apply cluster changes, and delete logs on the host.

Category levels, from 0 (none) to 3 (high)
Category	Level	Why
Code & shell execution	3 (high)	The shipped scripts execute commands directly, including `subprocess.run(..., shell=True, capture_output=True, text=True, timeout=300)` and many `kubectl`/`systemctl` calls, so the agent can run arbitrary shell operations.
Network access	2 (moderate)	It sends HTTP requests to monitoring and health endpoints such as `http://prometheus:9090/api/v1/query?...` and `http://localhost:8080/health`, which moves operational data over the network.
Filesystem reach	2 (moderate)	It explicitly deletes system logs with `find /var/log -name "*.log" -mtime "+7" -delete`, which reaches outside the project into a sensitive system path.
Secrets & credentials	0 (none)	The files do not explicitly read or request tokens, passwords, key material, `.env` files, or browser/CLI credential stores.
Privilege & persistence	3 (high)	The examples require elevated host and cluster privileges, e.g. `systemctl restart myservice`, `tc qdisc add ...`, `iptables`, and `kubectl exec`, all of which typically need admin or cluster access.
Instruction hijack surface	0 (none)	I did not find instructions to ignore safeguards, follow remote instructions, hide actions, or otherwise steer the agent around its normal controls.
Irreversible actions	3 (high)	The skill is meant to perform live remediation and chaos actions such as `kubectl delete`, `kubectl rollout undo`, `kubectl scale`, and automated restart logic, so it can change production state without manual execution each time.
Transparency	0 (none)	All shipped content is readable markdown and inline code; there are no binaries, hidden payloads, or decoded-at-runtime installers.

Before installing

Read `references/automation-toil.md` for `shell=True`, `systemctl`, and `/var/log` deletion before allowing it anywhere near a real host.
Run it first in a disposable staging cluster or VM with non-production `kubectl` context and fake Prometheus data.
Confirm whether you are comfortable granting root/cluster-admin style actions (`iptables`, `tc`, pod deletes, rollbacks).

Rated 2026-10-20 by an automated review of 6 files from the skill's repository.

Source

Repository: Jeffallan/claude-skills (all skills from this repository)
Path: skills/sre-engineer/SKILL.md
Branch: main
Updated: 2026-09-19

cloud-architect — Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure.
agents-deploy — Use when deploying your agent to AWS, or when a deploy has failed.
aws-compute — Provisions, scales, and operates Amazon EC2 virtual-machine workloads: instance-type selection (Graviton/Arm64, burstable T credits, GPU.
devcontainer-setup — Creates devcontainers with Claude Code, language-specific tooling (Python/Node/Rust/Go), and persistent volumes.
chaos-engineer — Designs chaos experiments, creates failure injection frameworks, and facilitates game day exercises for distributed systems — producing runbooks.
kubernetes-specialist — Use when deploying or managing Kubernetes workloads.