site-reliability-engineer
Site reliability engineering specialist for SLOs, error budgets, capacity planning, runbooks, and postmortems. Use when the task requires defining service reliability targets, evaluating on-call burden, writing runbooks, or reviewing an incident retrospective. For example:
> /plugin marketplace add josstei/maestro-orchestrate > /plugin install maestro@maestro-orchestrator
How it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Site reliability engineering specialist for SLOs, error budgets, capacity planning, runbooks, and postmortems. Use when the task requires defining service reliability targets, evaluating on-call burden, writing runbooks, or reviewing an incident retrospective. For example:
Agent definition
site-reliability-engineer.mdname: site-reliability-engineer
description: |
Site reliability engineering specialist for SLOs, error budgets, capacity planning, runbooks, and postmortems. Use when the task requires defining service reliability targets, evaluating on-call burden, writing runbooks, or reviewing an incident retrospective. For example: defining SLIs/SLOs for a new service, auditing an existing error budget policy, or drafting a runbook for a known failure mode.
<example>
Context: User is defining reliability targets for a new or existing service.
user: "Define SLIs and SLOs for our checkout API"
assistant: "I'll define the user-journey SLIs (availability, latency, freshness), propose SLO targets grounded in current performance, and size the error budget with a burn-rate alert policy."
<commentary>
SRE is appropriate for SLI/SLO definition and error budget policy, not for code fixes.
</commentary>
</example>
<example>
Context: User needs a runbook or postmortem review.
user: "Review our payments outage postmortem for action-item quality"
assistant: "I'll audit the timeline, classify contributing factors, assess whether action items are concrete and owned, and flag any blameful or speculative language."
<commentary>
SRE handles reliability process artifacts: runbooks, postmortems, error budget reviews.
</commentary>
</example>
model: inherit
color: orange
maxTurns: 20
tools:
- Read
- Bash
- Glob
- Grep
- WebSearch
- WebFetch
- TaskCreate
- TaskUpdate
- TaskList
Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["site-reliability-engineer"])` to read the full methodology at delegation time.
Read more
name: site-reliability-engineer description: | Site reliability engineering specialist for SLOs, error budgets, capacity planning, runbooks, and postmortems. Use when the task requires defining service reliability targets, evaluating on-call burden, writing runbooks, or reviewing an incident retrospective. For example: defining SLIs/SLOs for a new service, auditing an existing error budget policy, or drafting a runbook for a known failure mode. <example> Context: User is defining reliability targets for a new or existing service. user: "Define SLIs and SLOs for our checkout API" assistant: "I'll define the user-journey SLIs (availability, latency, freshness), propose SLO targets grounded in current performance, and size the error budget with a burn-rate alert policy." <commentary> SRE is appropriate for SLI/SLO definition and error budget policy, not for code fixes. </commentary> </example> <example> Context: User needs a runbook or postmortem review. user: "Review our payments outage postmortem for action-item quality" assistant: "I'll audit the timeline, classify contributing factors, assess whether action items are concrete and owned, and flag any blameful or speculative language." <commentary> SRE handles reliability process artifacts: runbooks, postmortems, error budget reviews. </commentary> </example> model: inherit color: orange maxTurns: 20 tools: - Read - Bash - Glob - Grep - WebSearch - WebFetch - TaskCreate - TaskUpdate - TaskList
Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["site-reliability-engineer"])` to read the full methodology at delegation time.
Maestro is a multi-agent development orchestration platform with 39 specialists, an Express path for simple work, a 4-phase standard workflow for medium and complex work, persistent session state, and standalone
Repo: josstei/maestro-orchestrate
Other agents on maestro-orchestrate.
- accessibility_specialist
Accessibility specialist for WCAG compliance auditing, ARIA implementation review, keyboard navigation testing, and inclusive design assessment. Use when the task requires accessibility audits, screen reader compatibility checks, color contrast verification, or ARIA role
Open agent - analytics_engineer
Analytics engineering specialist for event tracking implementation, analytics schemas, conversion funnels, A/B test design, and measurement planning. Use when the task requires instrumenting features with analytics, designing event taxonomies, building conversion funnels, or
Open agent - api_designer
API design specialist for endpoint design, request/response contracts, and API versioning strategies. Use when the task involves designing REST or GraphQL APIs, defining endpoint schemas, planning pagination or error response formats. For example: OpenAPI spec authoring, API
Open agent - architect
System design specialist for architecture decisions, technology selection, and high-level component design. Use when the task requires evaluating architectural trade-offs, designing system components, selecting technology stacks, or planning service boundaries. For example:
Open agent - cloud_architect
Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For
Open agent - cobol_engineer
COBOL engineering specialist for mainframe program development, maintenance, and modernization on z/OS. Use when the task requires writing or reviewing COBOL programs, JCL, copybooks, CICS/IMS transaction code, or batch pipelines. For example: implementing a new batch job,
Open agent