deploy-and-monitor
starsforks
How to install deploy-and-monitor?
rlaope/oh-my-hermes/deploy-and-monitor
$npx -y skills add rlaope/oh-my-hermes --skill deploy-and-monitor[omh] Hermes Deploy-and-Monitor workflow: release checklist, deploy decision, health signals, rollback gate, and post-deploy status.
SKILL.md
| 1 | # Deploy And Monitor |
| 2 | |
| 3 | This is a Hermes-native `deploy-and-monitor` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `deploy-and-monitor` exists to keep `monitoring` 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: deploy-and-monitor: prepare the release monitor, rollback signals, health checks, and post-deploy status card. |
| 19 | - Expected behavior: Create release monitoring guidance with deployment, metric, rollback, and observation boundaries. |
| 20 | - Why: The request is about deploy readiness and monitoring rather than code review alone. |
| 21 | |
| 22 | Bad example: |
| 23 | |
| 24 | - Prompt: deploy-and-monitor: 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 `deploy-and-monitor`. |
| 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: **Coding handoff** (`idea-to-deploy`, `cto-loop`, `deploy-and-monitor`, `code-review`, `build-failure-triage`, `verification-gate`, `security-safety-review`, `ultrawork`, `+7 more`) - coding owners, handoffs, review, CI, and merge evidence. |
| 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 prepare or narrate a release operation with deploy checklist, health signals, rollback criteria, and post-deploy status without pretending to run infrastructure. |
| 54 | |
| 55 | Strong routing signals: `deploy-and-monitor`, `deploy and monitor`, `deploy monitor`, `deployment monitoring`, `release monitor`, `post deploy`, `post-deploy`, `rollback`, `rollback gate`, `health check`, `incident watch`, `release health`, `deploy this service`, `배포 모니터링`, `서비스 배포`, `프로덕션 배포`, `인프라에 배포`, `배포 감시`, `롤백`, `헬스 체크`, `장애 감시`, `릴리즈 모니터링` |
| 56 | |
| 57 | ## Catalog Metadata |
| 58 | |
| 59 | Category: `monitoring` |
| 60 | Phase: `release-ops` |
| 61 | Hermes role: `operator` |
| 62 | Quality tier: `release-gated` |
| 63 | |
| 64 | Quality bar: |
| 65 | |
| 66 | - Name release scope, target environment, health signals, rollback criteria, and evidence owner. |
| 67 | - Show pre-deploy, deploy decision, monitor, rollback, and post-deploy record as distinct stages. |
| 68 | - Mark health and rollback status unknown until observed evidence arrives. |
| 69 | - Convert fix follow-ups into separate accepted plans or executor handoffs. |
| 70 | |
| 71 | Handoff policy: |
| 72 | |
| 73 | Keep release checklist, health criteria, rollback gates, and status narration in Hermes; record deploy, monitor, incident, or rollback evidence only when the wrapper or operator observes it. |
| 74 | |
| 75 | Required inputs: |
| 76 | |
| 77 | - release scope |
| 78 | - environment |
| 79 | - health signals |
| 80 | - rollback owner |
| 81 | |
| 82 | Expected outputs: |
| 83 | |
| 84 | - pre-deploy checklist |
| 85 | - deploy decision gate |
| 86 | - monitoring watchlist |
| 87 | - rollback criteria |
| 88 | - post-deploy status boundary |
| 89 | |
| 90 | Artifact expectations: |
| 91 | |
| 92 | - release opera |
People who liked this also viewed
6 picksType
- microsoft-foundryDeploy, evaluate, fine-tune, and manage Foundry agents end-to-end with azd: hosted agent scaffold/run/deploy, prompt agent create, batch eval, continuous eval, prompt optimizer, Agent Optimizer scaffoSkillsJul 2026
- azure-deployExecute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application SkillsJul 2026
- azure-preparePrepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wSkillsJul 2026
- azure-validate--- name: azure-validate description: "Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity pSkillsJul 2026
- azure-aigatewayConfigure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: semantic caching, token limit, content safety, load balancing, AI model governance, MCP rate limiting, jailbSkillsJul 2026
- azure-hosted-copilot-sdkOfficial agent plugin providing skills and MCP server configurations for Azure scenarios.SkillsJul 2026
