reliability-review
starsforks
How to install reliability-review?
rlaope/oh-my-hermes/reliability-review
$npx -y skills add rlaope/oh-my-hermes --skill reliability-review[omh] Hermes Reliability Review workflow: postmortems, SLOs, error budgets, incident follow-ups, and service reliability evidence.
SKILL.md
| 1 | # Reliability Review |
| 2 | |
| 3 | This is a Hermes-native `reliability-review` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `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. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The user only needs a generic status report or leadership deck. |
| 12 | - No service, incident, SLO, metric, or reliability source boundary is available. |
| 13 | - The request is implementation of remediation rather than review of reliability evidence. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: reliability-review 장애 포스트모템과 SLO 에러버짓 상태를 검토해줘. |
| 20 | - Expected behavior: Prepare a reliability artifact that separates metrics/references, assumptions, missing evidence, and remediation follow-ups. |
| 21 | - Why: The request is reliability evidence review with closure-sensitive claims. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: reliability-review make a monthly PPT report for leadership. |
| 26 | - Expected behavior: Use `report-package` unless the report specifically asks for reliability evidence review. |
| 27 | - Why: Report packaging and reliability validation are independent operations surfaces. |
| 28 | |
| 29 | ## Completion Checklist |
| 30 | |
| 31 | - Confirm the workflow target, evidence boundary, and stop condition are named. |
| 32 | - Report which outputs are prepared, observed, blocked, or missing. |
| 33 | - Name the smallest next verification or handoff instead of claiming completion from narration. |
| 34 | |
| 35 | ## Recovery Notes |
| 36 | |
| 37 | - If required context is missing, ask one blocking question or route back to the narrower workflow. |
| 38 | - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action. |
| 39 | |
| 40 | ## OMH Context Rail |
| 41 | |
| 42 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 43 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 44 | - Current lane: **Research and company ops** (`source-finder`, `web-research`, `best-practice-research`, `autoresearch-goal`, `research-brief`, `strategy-brief`, `feedback-triage`, `research-department`, `+6 more`) - research, signals, ops, and briefings. |
| 45 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 46 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 47 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 48 | - Coverage: Every generated workflow skill carries this rail. |
| 49 | - Normal users talk to Hermes; OMH CLI is infra. |
| 50 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 51 | |
| 52 | ## Use When |
| 53 | |
| 54 | Use when Hermes should review incident notes, SLOs, error budgets, or service reliability evidence while keeping remediation and closure claims observed. |
| 55 | |
| 56 | 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`, `장애 리뷰`, `장애 회고`, `포스트모템`, `사후 분석`, `에러버짓`, `에러 버짓`, `서비스 신뢰성`, `신뢰성 검증`, `재발 방지` |
| 57 | |
| 58 | ## Catalog Metadata |
| 59 | |
| 60 | Category: `reliability` |
| 61 | Phase: `incident-and-slo-review` |
| 62 | Hermes role: `operator` |
| 63 | Quality tier: `reliability-gated` |
| 64 | |
| 65 | Quality bar: |
| 66 | |
| 67 | - Name service, incident/time window, SLO/error-budget target, source references, and missing observations. |
| 68 | - Separate supplied metrics, incident notes, assumptions, and remediation follow-ups. |
| 69 | - Keep closure and remediation status unobserved until evidence is supplied. |
| 70 | |
| 71 | Handoff policy: |
| 72 | |
| 73 | 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. |
| 74 | |
| 75 | Required inputs: |
| 76 | |
| 77 | - service or incident scope |
| 78 | - time window |
| 79 | - metric/source references |
| 80 | - known remediation items or gaps |
| 81 | |
| 82 | Expected outputs: |
| 83 | |
| 84 | - reliability review |
| 85 | - evidence and missing-evidence list |
| 86 | - remediation follow-up boundary |
| 87 | |
| 88 | Artifact expectations: |
| 89 | |
| 90 | - operation_artifact/v1 reliability-review artifact when a wrapper or CLI records it |
| 91 | |
| 92 | Safety rules: |
| 93 | |
| 94 | - Do not claim SLO pass, healthy error budget, incident closure, or remediation completion withou |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
