Chaos Engineer
Jeffallan/claude-skills
Designs chaos experiments, failure injection and game days for distributed systems, with blast radius limits, rollback plans and written learnings.
[omh] Postmortem for an outage or SLO miss: postmortems, SLOs, error budgets, incident follow-ups, and service reliability evidence.
Install Omh Reliability Review
$ npx skills add rlaope/oh-my-hermes --skill omh-reliability-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rlaope/oh-my-hermes omh-reliability-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/omh-reliability-review .claude/skills/omh-reliability-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "omh-reliability-review" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-reliability-review into .claude/skills/omh-reliability-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-reliability-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-reliability-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add rlaope/oh-my-hermes --skill omh-reliability-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rlaope/oh-my-hermes omh-reliability-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/omh-reliability-review .agents/skills/omh-reliability-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "omh-reliability-review" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-reliability-review into .agents/skills/omh-reliability-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-reliability-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rlaope/oh-my-hermes --skill omh-reliability-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rlaope/oh-my-hermes omh-reliability-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/omh-reliability-review .cursor/skills/omh-reliability-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "omh-reliability-review" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-reliability-review into .cursor/skills/omh-reliability-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-reliability-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/rlaope/oh-my-hermes.git --path skills/omh-reliability-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add rlaope/oh-my-hermes --skill omh-reliability-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rlaope/oh-my-hermes omh-reliability-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/omh-reliability-review .gemini/skills/omh-reliability-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "omh-reliability-review" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-reliability-review into .gemini/skills/omh-reliability-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-reliability-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install rlaope/oh-my-hermes omh-reliability-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add rlaope/oh-my-hermes --skill omh-reliability-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/omh-reliability-review .github/skills/omh-reliability-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "omh-reliability-review" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-reliability-review into .github/skills/omh-reliability-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-reliability-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rlaope/oh-my-hermes --skill omh-reliability-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rlaope/oh-my-hermes omh-reliability-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/omh-reliability-review .opencode/skills/omh-reliability-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "omh-reliability-review" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-reliability-review into .opencode/skills/omh-reliability-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-reliability-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
omh-reliability-review- GitHub stars
- 3.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 727 words
- Files
- 1
- Skills in repo
- 143
- Repo updated
- First seen
- Licence
- MIT
At a glance
[omh] Postmortem for an outage or SLO miss: postmortems, SLOs, error budgets, incident follow-ups, and service reliability evidence.
- The user says: reliability-review
- SKILL.md covers Why This Exists, Do Not Use When, Examples and Completion Checklist, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Reliability review
What it does
Omh Reliability Review is an agent skill from rlaope/oh-my-hermes. [omh] Postmortem for an outage or SLO miss: postmortems, SLOs, error budgets, incident follow-ups, and service reliability evidence. Use when the user says: reliability-review, reliability review, incident review, incident postmortem, postmortem, post-mortem, slo review, slo.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Site reliability engineering and Runbooks and postmortems. The repository describes itself as: All in one plugin for Hermes Agent ⚚ the coding intelligence, a long-term memory system and model optimized workflow packages. The licence is MIT.
When your agent uses it
- The user says: reliability-review
- Reliability review
- Incident review
- Incident postmortem
Example prompts
- “/omh-reliability-review”
What it can do on your machine
Read from SKILL.md and the folder at commit 7cd0d02. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Omh Reliability Review loads about 1.6k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 727 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from rlaope/oh-my-hermes at commit 7cd0d02, republished under its MIT licence (© rlaope). 727 words, ~1,610 tokens.
Download SKILL.mdSave it as
.claude/skills/omh-reliability-review/SKILL.md (or your agent's skills folder).- name
- omh-reliability-review
- description
- [omh] Postmortem for an outage or SLO miss: postmortems, SLOs, error budgets, incident follow-ups, and service reliability evidence. Use when the user says: reliability-review, reliability review, incident review, incident postmortem, postmortem, post-mortem, slo review, slo.
Reliability Review
This is a Hermes-native reliability-review workflow skill.
Why This Exists
reliability-review exists to make SRE-style review strict: service reliability claims must point to metrics or references, and remediation remains separate from the review narrative.
Do Not Use When
- The user only needs a generic status report or leadership deck.
- No service, incident, SLO, metric, or reliability source boundary is available.
- The request is implementation of remediation rather than review of reliability evidence.
- The incident is still open and the user needs severity declared, a commander assigned, a running timeline, and recovery verified; use
live-incident-responseand review it once it is closed.
Examples
Good example:
- Prompt: reliability-review 장애 포스트모템과 SLO 에러버짓 상태를 검토해줘.
- Expected behavior: Prepare a reliability artifact that separates metrics/references, assumptions, missing evidence, and remediation follow-ups.
- Why: The request is reliability evidence review with closure-sensitive claims.
Bad example:
- Prompt: reliability-review make a monthly PPT report for leadership.
- Expected behavior: Use
report-packageunless the report specifically asks for reliability evidence review. - Why: Report packaging and reliability validation are independent operations surfaces.
Completion Checklist
- Confirm the workflow target, evidence boundary, and stop condition are named.
- Report which outputs are prepared, observed, blocked, or missing.
- Name the smallest next verification or handoff instead of claiming completion from narration.
Recovery Notes
- If required context is missing, ask one blocking question or route back to the narrower workflow.
- If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
Workflow Lane
- Current lane: Research and company ops (
product-docs,source-finder,web-research,research,model-optimization,inference-serving,model-finetuning,research-brief,+20 more) - research, signals, ops, and briefings. - If intent belongs to another lane, hand back to
oh-my-hermesor name the adjacent workflow. - Shared product, routing, compatibility, and evidence rules:
omh-routing/references/skill-common-rail.md.
Use When
Use when Hermes should review incident notes, SLOs, error budgets, or service reliability evidence while keeping remediation and closure claims observed.
Strong routing signals: `reliability-review`, `reliability review`, `incident review`, `incident postmortem`, `postmortem`, `post-mortem`, `slo review`, `slo`, `sla`, `error budget`, `service reliability`, `reliability followup`, `remediation tracking`, `sre review`, `장애 리뷰`, `장애 회고`, `포스트모템`, `사후 분석`, `에러버짓`, `에러 버짓`, `서비스 신뢰성`, `신뢰성 검증`, `재발 방지`Catalog Metadata
Category: reliability
Phase: incident-and-slo-review
Hermes role: operator
Quality tier: reliability-gated
Reasoning demand: standard
Quality bar:
- Name service, incident/time window, SLO/error-budget target, source references, and missing observations.
- Separate supplied metrics, incident notes, assumptions, and remediation follow-ups.
- Keep closure and remediation status unobserved until evidence is supplied.
Handoff policy:
Keep incident/SLO/error-budget review in Hermes; prepare remediation handoffs only after an accepted fix direction exists and record closure only from observed evidence.
Required inputs:
- service or incident scope
- time window
- metric/source references
- known remediation items or gaps
Expected outputs:
- reliability review
- evidence and missing-evidence list
- remediation follow-up boundary
Artifact expectations:
- omh_operation_artifact/v1 reliability-review artifact when a wrapper or CLI records it
Artifact contracts:
This label denotes the machine-enforcement level, not a skill quality score and not an observed evidence state.
- contract_id:
omh_operation_artifact/v1; enforcement_level:shared_operation_validated; consumer_id:validate_operation_artifact
Safety rules:
- Do not claim SLO pass, healthy error budget, incident closure, or remediation completion without source, metric, or reference evidence.
- Do not treat a reliability narrative as verification, review, CI, merge, or deploy evidence.
- Route code remediation through a separate accepted plan or executor handoff.
Show full SKILL.md (192 more words)Show less
Runtime Evidence
Preferred harness for this skill: reliability-review.
omh runtime record --skill reliability-review --harness reliability-review --status startedRecord observed delegation results; otherwise return not_available or not_observed.
Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes. Preserve workflow intent and stop conditions; verify before claiming completion. Reply in the user's own words and the host's own voice: its SOUL.md persona owns reply language, tone, speech level, and sentence endings, progress updates included (where it sets no language, use the one the user wrote in), and OMH shapes structure and content only; OMH's record terms (surface, lane, wrapper, handoff, evidence boundary, not_observed) stay in records and tool calls, never in the sentence the user reads unless they ask about one; and when a stop condition or a decision the user owns ends the turn, offer the next action as a question rather than declaring what will not be done.
Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
Shared product, compatibility, topology, memory, harness, and execution rules: omh-routing/references/skill-common-rail.md. Load it when applicable; otherwise name an unavailable capability.
© rlaope, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/omh-reliability-review of rlaope/oh-my-hermes.
Open the folder on GitHubat commit 7cd0d02
Compare with similar skills
Omh Reliability Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Omh Reliability Review this skillrlaope/oh-my-hermes | 3.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Chaos EngineerJeffallan/claude-skills | 12k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Error HandlerEliasOulkadi/shokunin | 114 | — | ~3.6k | Automated safety check: Notes | MIT | |
| SRE EngineerJeffallan/claude-skills | 12k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Incident ResponderDokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI | 508 | — | ~706 | Automated safety check: Pass | Custom licence | |
| Mint Enrollfullsend-ai/fullsend | 150 | — | ~3.6k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Error Handler
EliasOulkadi/shokunin
Design error handling, structured logging, and observability with OpenTelemetry (traces, metrics, logs), error classification, recovery patterns (retry with jitter, circuit breaker, bulkhead…
SRE Engineer
Jeffallan/claude-skills
Defines SLIs, SLOs and error budgets, and sets up golden-signal monitoring, blameless postmortems, toil automation and chaos experiments for production systems.
Incident Responder
Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI
Expert SRE incident responder specializing in rapid problem resolution.
Mint Enroll
fullsend-ai/fullsend
SRE runbook for enrolling new GitHub repos into the fullsend token mint service using go run ./cmd/fullsend from this checkout.
Knowledge Ops
alirezarezvani/claude-skills
A skill your agent uses when a Head of Ops, Knowledge Manager, or TPM-Internal needs to author, validate, or clean up company SOPs and internal runbooks (procurement intake, vendor offboarding…
More from rlaope/oh-my-hermes
All 143 skills in this repoOmh Accessibility Audit
rlaope/oh-my-hermes
[omh] Screen-reader or keyboard accessibility gaps: prepare WCAG, keyboard, focus, screen-reader, target-size, and reflow evidence gates for UI surfaces.
Omh Agent Debug
rlaope/oh-my-hermes
[omh] Agent is stuck, looping, or drifting: capture a stuck, looping, drifting, or repeatedly failing agent run, diagnose the likely failure pattern, and prepare the smallest safe recovery action.
Omh Agent Evaluation
rlaope/oh-my-hermes
[omh] Choosing between coding agents on evidence: compare executor or agent choices on reproducible tasks using quality, cost, time, tool, and evidence metrics.
Omh Agent Instructions
rlaope/oh-my-hermes
[omh] Agent instruction file for a repo -- AGENTS.md, CLAUDE.md, a Cursor rule: write or update what an agent cannot derive from the code, inside a marked region, with every command verified or…
Omh Agent Ops Review
rlaope/oh-my-hermes
[omh] AI agent progress for managers: help managers inspect AI-agent progress, blockers, quality gates, and throughput levers.
Omh AI Slop Cleaner
rlaope/oh-my-hermes
[omh] Messy or AI-generated code to clean up: delete AI-generated slop, dead code, and duplication while observable behavior stays identical.
Related
Categories
Questions about Omh Reliability Review
What does Omh Reliability Review do?
[omh] Postmortem for an outage or SLO miss: postmortems, SLOs, error budgets, incident follow-ups, and service reliability evidence. Omh Reliability Review is an agent skill from rlaope/oh-my-hermes. [omh] Postmortem for an outage or SLO miss: postmortems, SLOs, error budgets, incident follow-ups, and service reliability evidence.
When should I use Omh Reliability Review?
Omh Reliability Review fits situations like: the user says: reliability-review; reliability review; incident review; incident postmortem.
How do I install Omh Reliability Review in Claude Code?
Run `npx skills add rlaope/oh-my-hermes --skill omh-reliability-review -a claude-code`. Or copy the skill folder (skills/omh-reliability-review in rlaope/oh-my-hermes) into .claude/skills/omh-reliability-review in your project. Claude Code loads it when a task matches its description.
How do I install Omh Reliability Review in Codex?
Run `npx skills add rlaope/oh-my-hermes --skill omh-reliability-review -a codex`. Or copy the skill folder (skills/omh-reliability-review in rlaope/oh-my-hermes) into .agents/skills/omh-reliability-review in your project. Codex loads it when a task matches its description.
Can I use Omh Reliability Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rlaope/oh-my-hermes --skill omh-reliability-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/omh-reliability-review, .gemini/skills/omh-reliability-review, .github/skills/omh-reliability-review and .opencode/skills/omh-reliability-review in your project.
What does Omh Reliability Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Omh Reliability Review is instructions for the agent only.
Does Omh Reliability Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Omh Reliability Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Omh Reliability Review use?
Omh Reliability Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Omh Reliability Review use?
About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Omh Reliability Review?
Skills that share tags, products or a category with Omh Reliability Review: Chaos Engineer (Jeffallan/claude-skills, 12k stars), Error Handler (EliasOulkadi/shokunin, 114 stars), SRE Engineer (Jeffallan/claude-skills, 12k stars) and Incident Responder (Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI, 508 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Omh Reliability Review?
rlaope (a GitHub user) maintains it in rlaope/oh-my-hermes, which has 3,243 GitHub stars. The repository holds 143 skills in this directory. The repository was last updated on October 10, 2026.
Source: rlaope/oh-my-hermes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.