Individual skill
hermes-production-ops
Operate and maintain a live production Hermes gateway deployment: switch models/providers globally, manage gateway restarts, suppress operational notifications to end-users, tune streaming/progress config for messaging platforms, and recover from stuck states without sudo. Use when changing the global model, planning a gateway restart, or configuring platform behavior for end-user-facing deployments.
skills/hermes-production-ops/SKILL.md
Source commit 70a22739efb5650a27fedba4082ba48b1d53e9fd
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 127
- Repository last updated
- Sep 11, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- devops Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 8,023 bytesSKILL.mdcore · 8,023 bytesSKILL.mdcore · 8,023 bytesSKILL.mdcore · 8,023 bytesreferences/gateway-restart-notifications.mddoc · 3,694 bytesreferences/gateway-streaming-config.mddoc · 3,800 bytes
Read excerpt
# Hermes Production Gateway Operations
Techniques for operating a live production Hermes gateway that serves
non-technical end-users via Telegram (or other messaging platforms). The
core constraint: **the gateway cannot go down** and **end-users should not
see operational noise** (restart pings, progress spam, error messages,
technical detail).
## When to Use
- Switching the global model or provider (e.g., GLM-5.2 → GLM-5.3)
- Suppressing gateway restart/startup notifications to end-users
- Tuning streaming/progress config for a messaging deployment
- Planning a gateway restart that minimizes disruption