reliability-engineering

Name: reliability-engineering
Availability: InStock
Author: JCETools-Petra

Convert reliability requirements into SLO/SLI definitions, error-budget policies, and chaos experiment plans.

16|Updated Apr 30, 2026

Search Tags:#incident response #load testing #chaos engineering #postmortem #error budget #slo #litmus

Ready to run

npx skills add https://github.com/JCETools-Petra/JCE-Opencode-Tools --skill reliability-engineering-jcetools-petra

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reliability-engineering
Source: https://github.com/JCETools-Petra/JCE-Opencode-Tools/tree/main/config/skills/reliability-engineering
Command: npx skills add https://github.com/JCETools-Petra/JCE-Opencode-Tools --skill reliability-engineering-jcetools-petra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams prevent outages and reduce impact by turning reliability goals into measurable SLOs/SLIs, managing error budgets, validating resilience with chaos experiments, and running consistent incident and postmortem workflows.

Core Features & Use Cases

SLO/SLI Design: Selects appropriate SLIs (availability, latency, freshness, correctness, durability, error rate) and sets practical targets and windows by service type.
Error Budget Governance: Translates remaining error budget into clear deployment and experimentation rules to guide safe shipping decisions.
Chaos Engineering & Incident Response: Provides a structured chaos progression plan (e.g., Litmus experiments) and a severity-driven incident commander workflow with verification and follow-up.

Quick Start

Use this Skill to draft an SLO and error-budget policy for your service, then outline a chaos experiment and an incident response runbook for the same scope.

Frequently Asked Questions about reliability-engineering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I define SLOs and SLIs for user-facing APIs and data pipelines?▼

Defining SLOs involves selecting appropriate SLIs such as availability, latency, and error rate, then setting practical targets and windows tailored to your service type to quantify reliability goals.

How does error budget governance guide safe deployment decisions?▼

Error budget governance translates remaining error budget into clear deployment and experimentation rules, governing safe shipping decisions by restricting releases when burn rates indicate insufficient reliability margin.

How do I create a Litmus-style chaos engineering experiment plan?▼

Creating a chaos experiment plan involves generating Litmus-style experiment scaffolding that provides a structured progression to validate system resilience by injecting failures and verifying operational readiness.

What is included in a severity-driven incident response workflow?▼

A severity-driven incident response workflow includes an incident commander process, operational readiness verification, and a structured postmortem follow-up to safely resolve outages and prevent recurrence.

Can I use this for load testing and operational readiness verification of async workers?▼

Yes, you can apply this to async workers and storage systems, generating a load-testing strategy and verifying operational readiness alongside SLO definitions and incident response procedures.

What is the best way to structure a postmortem after an incident?▼

The best way to structure a postmortem is using a severity-to-response incident process that documents verification steps and follow-up actions, ensuring actionable improvements for future reliability.