Back to catalog
Human reviewedAutomation

Skill dossier

sre-engineer

Source declaration

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.

The author's original description, preserved in English. It describes intent, not verified performance.

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.

automationreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

Covers site reliability work: define SLIs and SLOs, compute error budgets, build golden-signal monitoring, reduce toil and design chaos experiments.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Defines quantitative SLOs and calculates error budgets from them.
  • Builds monitoring and alerting config such as Prometheus burn-rate rules.
  • Identifies repetitive tasks and writes automation scripts.
  • Designs chaos experiments and verifies recovery against RTO/RPO targets.

Limitations & scope

  • Examples assume Prometheus and Kubernetes; other stacks need adaptation.
  • Alert thresholds and runbook URLs in examples are placeholders.
  • Chaos experiments need a safe target environment, which the skill does not provide.

Relevant for

  • SRE and on-call engineers
  • Platform teams setting reliability targets
  • Teams adopting error budget policies

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
65.2 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/sre-engineer/references/automation-toil.mdReference14.5 KB
skills/sre-engineer/references/error-budget-policy.mdReference9.6 KB
skills/sre-engineer/references/incident-chaos.mdReference16.4 KB
skills/sre-engineer/references/monitoring-alerting.mdReference11.3 KB
skills/sre-engineer/references/slo-sli-management.mdReference6.6 KB
skills/sre-engineer/SKILL.mdInstruction6.8 KB

SKILL.md frontmatter

{
  "name": "sre-engineer",
  "description": "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.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "devops",
    "triggers": "SRE, site reliability, SLO, SLI, error budget, incident management, chaos engineering, toil reduction, on-call, MTTR",
    "role": "specialist",
    "scope": "implementation",
    "output-format": "code",
    "related-skills": "devops-engineer, cloud-architect, kubernetes-specialist"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Assess reliability

    Review architecture, SLOs, incidents and toil levels.

  2. 02
    Action

    Define SLOs

    Identify meaningful SLIs and set appropriate targets.

  3. 03
    Decision

    Verify alignment

    Confirm SLO targets reflect user expectations before proceeding.

  4. 04
    Output

    Deliver SRE artifacts

    Provide SLO definitions, alerting config, automation scripts, runbooks and a short reliability-impact note.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

118 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Note

File modification is described or implemented

102 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 102 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

16 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 16 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Review any generated kubectl or restart automation and chaos experiments before running them against live systems.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/sre-engineer # .claude/skills/sre-engineer
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/sre-engineer/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Copy the skill directory into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Confirm SKILL.md is discoverable at the destination, then ask Claude Code to use sre-engineer on a small task.

Prerequisites

  • Examples assume Prometheus and Kubernetes; other stacks need adaptation.
  • Alert thresholds and runbook URLs in examples are placeholders.
  • Chaos experiments need a safe target environment, which the skill does not provide.

Example prompts

Representative task

Use the sre-engineer skill to define a 99.9% availability SLO for our checkout API, calculate the 30-day error budget, and draft multiwindow burn-rate alerts with runbook links.

Inspect before use

Read the sre-engineer skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/sre-engineer/SKILL.md. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Includes a worked error-budget calculation and burn-rate alert example.
  • Requires blameless postmortems and justification of SLOs by user impact.

Considerations

  • The bundled auto-remediation script restarts deployments via kubectl and needs careful scoping.
  • SLO targets still require human judgment about user expectations.
Research conclusion

A useful SRE playbook for teams that want concrete SLO, alerting and toil-reduction templates.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/sre-engineer
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.