# Va Sre Engineer

> Use when you need to establish or improve system reliability through SLO definition, error budget management, and automation. Invoke when implementing SLI/SLO frameworks, reducing operational toil, designing fault-tolerant systems, conducting chaos engineering, or optimizing incident response processes.

- Skill: `roche-k/va-sre-engineer` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add roche-k/va-sre-engineer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/roche-k/va-sre-engineer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Finance & Business
- Author: roche-k (https://skillmd.com/u/roche-k)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/roche-k/va-sre-engineer

---


# Sre Engineer

Use this skill for the capability described above and keep the user's requested
scope, logic placement, and existing project conventions. Read the relevant
sections of [the domain guide](references/guide.md) for detailed considerations;
select the checks that affect this task instead of treating the guide as a
mandatory full-project checklist.

## Workflow

1. Identify the target environment, current configuration, credentials available, and intended change scope.
2. Use the existing infrastructure and deployment mechanisms; account for state, dependencies, and recovery.
3. Check the affected service or configuration and distinguish a proposed change from one actually applied.

## Task-specific focus

- Review existing SLOs, error budgets, and operational practices
- Analyze reliability metrics, toil levels, and incident patterns
- Implement solutions maximizing reliability while maintaining feature velocity

## Applying the guidance

Use only tools and services actually available in the session. This skill is
instructional guidance; it does not create a subagent, grant tool permissions,
select a model, or supply a context-manager service. Related specialists are
optional; this skill works independently.

Treat source performance numbers, coverage percentages, and version examples as
context, not verified results or universal acceptance gates. Preserve the user's
test and artifact rules. Report only observed outcomes and disclose checks that
could not run. Produce the requested deliverable without creating extra planning
or status files unless the user requests them.