ops-review
starsforks
How to install ops-review?
rlaope/oh-my-hermes/ops-review
$npx -y skills add rlaope/oh-my-hermes --skill ops-review[omh] Hermes Ops Review workflow: status, risks, blockers, priorities, and follow-ups.
SKILL.md
| 1 | # Ops Review |
| 2 | |
| 3 | This is a Hermes-native `ops-review` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `ops-review` exists to keep `operations` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence. |
| 12 | - The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed. |
| 13 | |
| 14 | ## Examples |
| 15 | |
| 16 | Good example: |
| 17 | |
| 18 | - Prompt: ops-review: summarize this week’s support queue, release blockers, owner status, and next operating risks. |
| 19 | - Expected behavior: Create an operations status review with owners, blockers, evidence gaps, and next actions. |
| 20 | - Why: The request is an operating review rather than a one-off plan or coding handoff. |
| 21 | |
| 22 | Bad example: |
| 23 | |
| 24 | - Prompt: ops-review: treat casual chat or unaccepted work as if this workflow already produced verified results. |
| 25 | - Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing `ops-review`. |
| 26 | - Why: The request lacks the required inputs or would overclaim work that Hermes did not observe. |
| 27 | |
| 28 | ## Completion Checklist |
| 29 | |
| 30 | - Confirm the workflow target, evidence boundary, and stop condition are named. |
| 31 | - Report which outputs are prepared, observed, blocked, or missing. |
| 32 | - Name the smallest next verification or handoff instead of claiming completion from narration. |
| 33 | |
| 34 | ## Recovery Notes |
| 35 | |
| 36 | - If required context is missing, ask one blocking question or route back to the narrower workflow. |
| 37 | - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action. |
| 38 | |
| 39 | ## OMH Context Rail |
| 40 | |
| 41 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 42 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 43 | - 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. |
| 44 | - 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. |
| 45 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 46 | - 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. |
| 47 | - Coverage: Every generated workflow skill carries this rail. |
| 48 | - Normal users talk to Hermes; OMH CLI is infra. |
| 49 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 50 | |
| 51 | ## Use When |
| 52 | |
| 53 | Use when Hermes should summarize observed status, risks, blockers, priorities, and follow-up actions for recurring operating work. |
| 54 | |
| 55 | Strong routing signals: `ops-review`, `ops review`, `weekly ops review`, `status review`, `operating review`, `release risks`, `risks and blockers`, `priorities`, `weekly status`, `운영 리뷰`, `주간 운영`, `상태 리뷰`, `리스크`, `블로커`, `우선순위`, `릴리즈 리스크` |
| 56 | |
| 57 | ## Catalog Metadata |
| 58 | |
| 59 | Category: `operations` |
| 60 | Phase: `status-review` |
| 61 | Hermes role: `operator` |
| 62 | Quality tier: `status-gated` |
| 63 | |
| 64 | Quality bar: |
| 65 | |
| 66 | - Tie every status claim to observed evidence or mark it as unknown. |
| 67 | - Separate risks, blockers, priorities, and follow-up owners. |
| 68 | - Keep code fixes as explicit follow-up handoffs, not implicit ops-review output. |
| 69 | |
| 70 | Handoff policy: |
| 71 | |
| 72 | Keep operating review and status narration in Hermes; delegate code fixes only from explicit accepted follow-up items. |
| 73 | |
| 74 | Required inputs: |
| 75 | |
| 76 | - status evidence |
| 77 | - scope |
| 78 | - time window |
| 79 | - known risks |
| 80 | |
| 81 | Expected outputs: |
| 82 | |
| 83 | - status summary |
| 84 | - risks |
| 85 | - blockers |
| 86 | - priorities |
| 87 | - follow-up actions |
| 88 | |
| 89 | Artifact expectations: |
| 90 | |
| 91 | - ops review record or status artifact when a wrapper captures it |
| 92 | |
| 93 | Safety rules: |
| 94 | |
| 95 | - Do not infer status from missing evidence. |
| 96 | - Separate observed facts, risks, blockers, decisions, and follow-up actions. |
| 97 | - Do not report review, CI, release, or merge readiness from an ops summary alone. |
| 98 | |
| 99 | ## Harness Discipline |
| 100 | |
| 101 | - Start from the representative harness registry in `oh-my-hermes` when the workflow needs coding, research, planning, goal execution, architecture, critique, QA, or documentation lanes. |
| 102 | - Prefer richer evidence and clearer stop conditions o |
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
