Shipping and Launch Checklist
addyosmani/agent-skills
Prepares a production launch with a pre-launch checklist, monitoring, a staged rollout and a rollback plan so every release is reversible and observable.
[omh] Release rollout needing health signals: release checklist, deploy decision, health signals, rollback gate, and post-deploy status.
Install Omh Deploy And Monitor
$ npx skills add rlaope/oh-my-hermes --skill omh-deploy-and-monitor -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rlaope/oh-my-hermes omh-deploy-and-monitor --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-deploy-and-monitor .claude/skills/omh-deploy-and-monitor && 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-deploy-and-monitor" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-deploy-and-monitor into .claude/skills/omh-deploy-and-monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-deploy-and-monitor", 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-deploy-and-monitorType 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-deploy-and-monitor -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rlaope/oh-my-hermes omh-deploy-and-monitor --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-deploy-and-monitor .agents/skills/omh-deploy-and-monitor && 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-deploy-and-monitor" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-deploy-and-monitor into .agents/skills/omh-deploy-and-monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-deploy-and-monitor", 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-deploy-and-monitor -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rlaope/oh-my-hermes omh-deploy-and-monitor --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-deploy-and-monitor .cursor/skills/omh-deploy-and-monitor && 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-deploy-and-monitor" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-deploy-and-monitor into .cursor/skills/omh-deploy-and-monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-deploy-and-monitor", 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-deploy-and-monitor--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-deploy-and-monitor -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rlaope/oh-my-hermes omh-deploy-and-monitor --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-deploy-and-monitor .gemini/skills/omh-deploy-and-monitor && 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-deploy-and-monitor" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-deploy-and-monitor into .gemini/skills/omh-deploy-and-monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-deploy-and-monitor", 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-deploy-and-monitorInstalls 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-deploy-and-monitor -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-deploy-and-monitor .github/skills/omh-deploy-and-monitor && 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-deploy-and-monitor" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-deploy-and-monitor into .github/skills/omh-deploy-and-monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-deploy-and-monitor", 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-deploy-and-monitor -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-deploy-and-monitor --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-deploy-and-monitor .opencode/skills/omh-deploy-and-monitor && 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-deploy-and-monitor" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-deploy-and-monitor into .opencode/skills/omh-deploy-and-monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-deploy-and-monitor", 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-deploy-and-monitor- GitHub stars
- 3.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 845 words
- Files
- 1
- Skills in repo
- 143
- Repo updated
- First seen
- Licence
- MIT
At a glance
[omh] Release rollout needing health signals: release checklist, deploy decision, health signals, rollback gate, and post-deploy status.
- The user says: deploy-and-monitor
- 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
- Deploy and monitor
What it does
Omh Deploy And Monitor is an agent skill from rlaope/oh-my-hermes. [omh] Release rollout needing health signals: release checklist, deploy decision, health signals, rollback gate, and post-deploy status. Use when the user says: deploy-and-monitor, deploy and monitor, deploy monitor, deployment monitoring, release monitor, post deploy, post-deploy, rollback.
Its SKILL.md is about 1.8k 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 Deployment and Feature launches and release readiness. 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: deploy-and-monitor
- Deploy and monitor
- Deployment monitoring
- Release monitor
Example prompts
- “/omh-deploy-and-monitor”
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 Deploy And Monitor loads about 1.8k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 845 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). 845 words, ~1,782 tokens.
Download SKILL.mdSave it as
.claude/skills/omh-deploy-and-monitor/SKILL.md (or your agent's skills folder).- name
- omh-deploy-and-monitor
- description
- [omh] Release rollout needing health signals: release checklist, deploy decision, health signals, rollback gate, and post-deploy status. Use when the user says: deploy-and-monitor, deploy and monitor, deploy monitor, deployment monitoring, release monitor, post deploy, post-deploy, rollback.
Deploy And Monitor
This is a Hermes-native deploy-and-monitor workflow skill.
Why This Exists
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.
Do Not Use When
- An incident has already been declared and the work is commanding it -- severity, commander, running timeline, recovery verification -- rather than watching a release; use
live-incident-response. - The ask is deciding a release before it ships -- what goes in, its version and tag, the canary stages, or which command rolls it back; use
release-cut, which writes the rollback trigger down before it is needed. - The change is to declared infrastructure itself -- a Terraform plan, a Kubernetes manifest, a Helm chart -- and needs its drift, blast radius, and cost delta read before it is applied; use
iac-change.
Examples
Good example:
- Prompt: deploy-and-monitor: prepare the release monitor, rollback signals, health checks, and post-deploy status card.
- Expected behavior: Create release monitoring guidance with deployment, metric, rollback, and observation boundaries.
- Why: The request is about deploy readiness and monitoring rather than code review alone.
Bad example:
- Prompt: deploy-and-monitor: treat casual chat or unaccepted work as if this workflow already produced verified results.
- Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing
deploy-and-monitor. - Why: The request lacks the required inputs or would overclaim work that Hermes did not observe.
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: Coding handoff (
idea-to-deploy,llm-app-dev,cto-loop,deploy-and-monitor,code-review,build-failure-triage,verification-gate,security-safety-review,+28 more) - coding owners, handoffs, review, CI, and merge evidence. - 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 prepare or narrate a release operation with deploy checklist, health signals, rollback criteria, and post-deploy status without pretending to run infrastructure.
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`, `배포 모니터링`, `서비스 배포`, `프로덕션 배포`, `인프라에 배포`, `배포 감시`, `롤백`, `헬스 체크`, `장애 감시`, `릴리즈 모니터링`Show full SKILL.md (429 more words)Show less
Catalog Metadata
Category: monitoring
Phase: release-ops
Hermes role: operator
Quality tier: release-gated
Reasoning demand: light
Quality bar:
- Name release scope, target environment, health signals, rollback criteria, and evidence owner.
- Show pre-deploy, deploy decision, monitor, rollback, and post-deploy as distinct stages.
- Mark health and rollback status unknown until observed evidence arrives.
Handoff policy:
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.
Required inputs:
- release scope
- environment
- health signals
- rollback owner
Expected outputs:
- pre-deploy checklist
- deploy decision gate
- monitoring watchlist
- rollback criteria
- post-deploy status boundary
Artifact expectations:
- release operation status record when the wrapper captures deploy or monitor observations
- web_qa_comparison/v1 for a canary only with a trusted host_deployment_observation/v1 and a production baseline captured before it
Artifact contracts:
This label denotes the machine-enforcement level, not a skill quality score and not an observed evidence state.
- contract_id:
deploy-and-monitor; enforcement_level:guidance_only; consumer_id:none
Safety rules:
- Do not claim deployment, health checks, rollback, or incident response happened from a prepared checklist.
- Keep release readiness, deploy decision, monitor signals, and rollback as separate evidence steps.
- Route code fixes discovered during monitoring as later executor handoffs.
- A canary web-QA comparison never authorizes rollback; a missing deployment observation is BLOCK and a field regression beyond tolerance is REVISE.
Runtime Evidence
Preferred harness for this skill: app-delivery-loop.
omh runtime record --skill deploy-and-monitor --harness app-delivery-loop --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.
- When wrapper metadata includes
memory_review_card/v1orhandoff_context_pack/v1, treat it as reviewed OMH-local or wrapper-supplied context only. Use conflict-free context summaries to shape plans and handoffs, but do not claim Hermes internal memory was read or changed. 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-deploy-and-monitor of rlaope/oh-my-hermes.
Open the folder on GitHubat commit 7cd0d02
Compare with similar skills
Omh Deploy And Monitor 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 Deploy And Monitor this skillrlaope/oh-my-hermes | 3.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Shipping and Launch Checklistaddyosmani/agent-skills | 105k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Onboarding Validationopen-edge-platform/edge-ai-suites | 140 | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| Frontmcp Production Readinessagentfront/frontmcp | 146 | — | ~6.5k | Automated safety check: Pass | Apache-2.0 | |
| Devops Rollout Plangithub/awesome-copilot | 40k | 1 repos | ~999 | Automated safety check: Pass | MIT | |
| Release ProcessFritzAndFriends/SharpSite | 145 | 1 repos | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Onboarding Validation
open-edge-platform/edge-ai-suites
Validate the get-started experience of Open Edge Platform (OEP) software components from the perspective of a first-time user.
Frontmcp Production Readiness
agentfront/frontmcp
Pre-production audit, hardening, and go-live checklists for FrontMCP servers.
- Official
Devops Rollout Plan
github/awesome-copilot
Generate comprehensive rollout plans with preflight checks, step-by-step deployment, verification signals, rollback procedures, and communication plans for infrastructure and application changes
Release Process
FritzAndFriends/SharpSite
Step-by-step release checklist for Squad — prevents v0.8.22-style disasters
Release Engineering
majiayu000/spellbook
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness.
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 Deploy And Monitor
What does Omh Deploy And Monitor do?
[omh] Release rollout needing health signals: release checklist, deploy decision, health signals, rollback gate, and post-deploy status. Omh Deploy And Monitor is an agent skill from rlaope/oh-my-hermes. [omh] Release rollout needing health signals: release checklist, deploy decision, health signals, rollback gate, and post-deploy status.
When should I use Omh Deploy And Monitor?
Omh Deploy And Monitor fits situations like: the user says: deploy-and-monitor; deploy and monitor; deployment monitoring; release monitor.
How do I install Omh Deploy And Monitor in Claude Code?
Run `npx skills add rlaope/oh-my-hermes --skill omh-deploy-and-monitor -a claude-code`. Or copy the skill folder (skills/omh-deploy-and-monitor in rlaope/oh-my-hermes) into .claude/skills/omh-deploy-and-monitor in your project. Claude Code loads it when a task matches its description.
How do I install Omh Deploy And Monitor in Codex?
Run `npx skills add rlaope/oh-my-hermes --skill omh-deploy-and-monitor -a codex`. Or copy the skill folder (skills/omh-deploy-and-monitor in rlaope/oh-my-hermes) into .agents/skills/omh-deploy-and-monitor in your project. Codex loads it when a task matches its description.
Can I use Omh Deploy And Monitor 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-deploy-and-monitor -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-deploy-and-monitor, .gemini/skills/omh-deploy-and-monitor, .github/skills/omh-deploy-and-monitor and .opencode/skills/omh-deploy-and-monitor in your project.
What does Omh Deploy And Monitor need to run?
SKILL.md names no scripts, command-line tools or credentials: Omh Deploy And Monitor is instructions for the agent only.
Does Omh Deploy And Monitor 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 Deploy And Monitor 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 Deploy And Monitor use?
Omh Deploy And Monitor 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 Deploy And Monitor use?
About 1.8k tokens (SKILL.md is roughly 7.1k 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 Deploy And Monitor?
Skills that share tags, products or a category with Omh Deploy And Monitor: Shipping and Launch Checklist (addyosmani/agent-skills, 105k stars), Onboarding Validation (open-edge-platform/edge-ai-suites, 140 stars), Frontmcp Production Readiness (agentfront/frontmcp, 146 stars) and Devops Rollout Plan (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Omh Deploy And Monitor?
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.