All skills
reliability-observability-gate
ProfessionalRuntime top levelUse analysis-agent to analyze recovery, SLO, capacity, degradation, and observability; task-agent to change resilience or telemetry; and review-agent to assess evidence. Skip self-review and no-runtime-impact work.
- Group
- Quality, security, reliability and delivery gates
- Routing mode
- evidence-only
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- reliability or recovery risk
- observability contract change
Do not use when
Anti-triggers — as binding as the triggers above
- no runtime behavior impact
- self review request
- unit test or local performance change with no runtime objective
- logging field-only change with no reliability decision
- release ordering only
- data correctness only
Required inputs
What must be supplied before this skill can decide anything
- acceptance
- failure behavior
Output contract
What this skill owes the next role
- failure model
- resilience changes
- reliability verdict
Escalation signals
When this skill must hand the decision back
- scope, authority, or material risk exceeds the selected task contract
Related expertise
12 Layer 3 candidates may be loaded behind this skill. A single task loads at most three, and only when the current evidence justifies them.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| checklist.mddecision-checklist | A bounded L2 mode needs compact checks for the triggered objective, telemetry, alert, dashboard, recovery, or runbook risk | The root contract is enough or mode-specific closure and targeted proof are required | AnalysisTaskReview |
| evidence-patterns.mdevidence-pattern | Closure depends on command/report artifacts, exit code, dashboard/alert proof, incident evidence, freshness, or proof limits | No reliability claim depends on runtime evidence or the body evidence contract is sufficient | AnalysisTaskReview |
| index.mdindex | competing reliability observability gate references require dependency, conflict, or output-fragment selection | the reliability observability gate root or a task-named reference already resolves selection | AnalysisTaskReview |
| reliability-output-and-gates.mdtargeted | L3-L5 work needs mode-specific closure and targeted gates for a selected objective, alert, resilience, telemetry, capacity/cost, recovery, or incident risk | A compact L1/L2 result is sufficient and no selected risk needs the extended proof contract | AnalysisTaskReview |
| solution-optimality.mdtargeted | An owned reliability objective, alert strategy, capacity bound, telemetry design, or failure-control choice has a material alternative | No owned objective or operational decision is affected, or current platform policy and evidence already determine the bounded control | AnalysisTaskReview |