Command Operator
This is a Hermes-native command-operator workflow skill.
Why This Exists
command-operator exists so Hermes users can ask for this workflow in chat and receive a structured, evidence-bounded OMH operating surface instead of ad hoc narration.
Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
Examples
Good example:
- Prompt: command-operator run npm test in the project terminal and summarize the output.
- Expected behavior: Produce
prepare_command_operator_card with required context, wrapper actions, and not-evidence boundaries.
- Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution.
Bad example:
- Prompt: command-operator run rm -rf without cwd, confirmation, or observation gates.
- Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened.
- Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence.
Completion Checklist
- Command text, working directory, environment assumptions, timeout, safety level, and stop condition are explicit.
- Destructive, credential, network, filesystem mutation, install, deploy, and production commands are gated or marked missing.
- Exit codes, stdout/stderr, test results, package-manager effects, and filesystem mutations are reported only from observed command evidence.
Recovery Notes
- If command text or working directory is missing, ask for the smallest missing scope needed before preparing the command task.
- If the command is destructive, credentialed, networked, install/deploy-oriented, or production-affecting, require an explicit confirmation gate.
- If the user supplied failed command output and asks for root cause, route to build-failure-triage or agent-debug instead of preparing a fresh command.
Workflow Lane
- Current lane: Automation and status (
achievements, workspace-audit, production-audit, automation-blueprint, github-event-ops, github-issue-intake, buzz, agent-board, +35 more) - schedules, status, health, and ops review.
- If intent belongs to another lane, hand back to
oh-my-hermes or 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 supervise terminal/CLI command execution without claiming the command ran or succeeded.
Strong routing signals: `command-operator`, `command operator`, `terminal command`, `terminal task`, `shell command`, `shell task`, `cli command`, `command execution`, `run command`, `run this command`, `execute command`, `execute this command`, `run npm test`, `run tests`, `npm test`, `pnpm test`, `bun test`, `uv run`, `python -m unittest`, `pytest`, `make test`, `cargo test`, `go test`, `summarize command output`, `터미널 명령`, `터미널에서`, `셸 명령`, `쉘 명령`, `명령 실행`, `명령어 실행`, `실행 준비`, `npm test 실행`, `테스트 실행`, `결과 요약`
Catalog Metadata
Category: command
Phase: command-task
Hermes role: guide
Quality tier: workflow-surface-gated
Reasoning demand: standard
Quality bar:
- Name the user-facing workflow objective, required context, next action, and stop condition.
- Separate prepared guidance from observed platform, runtime, connector, file, memory, or delivery evidence.
- Expose missing tools, credentials, targets, or observations as user-visible gaps.
- Choose the wait strategy before starting long-running work and bind it to a completion signal the host exposes, never to a status loop: a command that fits one tool call runs once in the foreground with a duration-sized timeout; a longer terminal command runs in the background with completion notification armed and no process-status polling; a delegated lane relies on its delivered result while the parent continues independent work or ends the turn; a CI, PR, deploy, file, port, log-line, or external-session condition uses the host's monitor when observed, else exactly ONE bounded watcher or adaptive backoff outside model turns. Record the handle and observation mode at dispatch; every armed wait needs a hard deadline, a cancellation path, and a fallback naming the missing capability. Each wait closes in one terminal state with bounded evidence; an unbounded idle or busy-wait is a defect and a lost notification times out. One decision-changing midpoint peek and any user-requested status check stay allowed; neither is the wait mechanism. Ladder and terminal states: shared rail.
Handoff policy:
Keep this as Hermes-facing orchestration guidance first. Prepare executor, connector, gateway, or host-runtime handoff only when the user accepts that next step and observed evidence can be recorded.
Required inputs:
- user request
- target context
- delivery or status expectation
- known missing evidence
Expected outputs:
- command_task_card/v1
- command_scope/v1
- command_safety_gate/v1
- command_result_manifest/v1 when observed
- next action
- prepared-vs-observed boundary
Artifact expectations:
- command_task_card/v1 metadata-only wrapper card when prepared
- command_scope/v1 with command text, working directory, environment assumptions, timeout, and stop condition
- command_safety_gate/v1 separating read-only, write/mutation, network, credential, and destructive-risk commands
- command_result_manifest/v1 only when exit code, stdout/stderr, logs, or terminal transcript are observed
Safety rules:
- A command operator card is not terminal launch, shell execution, package-manager action, test run, stdout/stderr capture, exit-code success, filesystem mutation, network access, or destructive command evidence unless observed command-result evidence records it.
- Do not claim connector, gateway, runtime, file generation, memory mutation, or host automation evidence from prepared guidance.
Runtime Evidence
Preferred harness for this skill: command-operator.
omh runtime record --skill command-operator --harness command-operator --status started
Record observed delegation results; otherwise return not_available or not_observed.
Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes.
Preserve workflow intent and stop conditions; verify before claiming completion.
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.
1---2name: omh-terminal3description: [omh] Policy overlay for terminal commands - add cwd, environment, safety, and result-evidence gates after preferring native shell tools for ordinary CLI, package-manager, and test runs. Use when the user says: command-operator, command operator, terminal command, terminal task, shell command, shell task, cli command, command execution.4---5
6# Command Operator
7
8This is a Hermes-native `command-operator` workflow skill.
9
10## Why This Exists
11
12`command-operator` exists so Hermes users can ask for this workflow in chat and receive a structured, evidence-bounded OMH operating surface instead of ad hoc narration.
13
14## Do Not Use When
15
16- The request is already handled by a narrower explicit skill with stronger evidence.
17- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
18- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
19
20## Examples
21
22Good example:
23
24- Prompt: command-operator run npm test in the project terminal and summarize the output.
25- Expected behavior: Produce `prepare_command_operator_card` with required context, wrapper actions, and not-evidence boundaries.
26- Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution.
27
28Bad example:
29
30- Prompt: command-operator run rm -rf without cwd, confirmation, or observation gates.
31- Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened.
32- Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence.
33
34## Completion Checklist
35
36- Command text, working directory, environment assumptions, timeout, safety level, and stop condition are explicit.
37- Destructive, credential, network, filesystem mutation, install, deploy, and production commands are gated or marked missing.
38- Exit codes, stdout/stderr, test results, package-manager effects, and filesystem mutations are reported only from observed command evidence.
39
40## Recovery Notes
41
42- If command text or working directory is missing, ask for the smallest missing scope needed before preparing the command task.
43- If the command is destructive, credentialed, networked, install/deploy-oriented, or production-affecting, require an explicit confirmation gate.
44- If the user supplied failed command output and asks for root cause, route to build-failure-triage or agent-debug instead of preparing a fresh command.
45
46## Workflow Lane
47
48- Current lane: **Automation and status** (`achievements`, `workspace-audit`, `production-audit`, `automation-blueprint`, `github-event-ops`, `github-issue-intake`, `buzz`, `agent-board`, `+35 more`) - schedules, status, health, and ops review.
49- If intent belongs to another lane, hand back to `oh-my-hermes` or name the adjacent workflow.
50- Shared product, routing, compatibility, and evidence rules: `omh-routing/references/skill-common-rail.md`.
51
52## Use When
53
54Use when Hermes should prepare or supervise terminal/CLI command execution without claiming the command ran or succeeded.
55
56 Strong routing signals: `command-operator`, `command operator`, `terminal command`, `terminal task`, `shell command`, `shell task`, `cli command`, `command execution`, `run command`, `run this command`, `execute command`, `execute this command`, `run npm test`, `run tests`, `npm test`, `pnpm test`, `bun test`, `uv run`, `python -m unittest`, `pytest`, `make test`, `cargo test`, `go test`, `summarize command output`, `터미널 명령`, `터미널에서`, `셸 명령`, `쉘 명령`, `명령 실행`, `명령어 실행`, `실행 준비`, `npm test 실행`, `테스트 실행`, `결과 요약`
57
58## Catalog Metadata
59
60Category: `command`
61Phase: `command-task`
62Hermes role: `guide`
63Quality tier: `workflow-surface-gated`
64Reasoning demand: `standard`
65
66Quality bar:
67
68- Name the user-facing workflow objective, required context, next action, and stop condition.
69- Separate prepared guidance from observed platform, runtime, connector, file, memory, or delivery evidence.
70- Expose missing tools, credentials, targets, or observations as user-visible gaps.
71- Choose the wait strategy before starting long-running work and bind it to a completion signal the host exposes, never to a status loop: a command that fits one tool call runs once in the foreground with a duration-sized timeout; a longer terminal command runs in the background with completion notification armed and no process-status polling; a delegated lane relies on its delivered result while the parent continues independent work or ends the turn; a CI, PR, deploy, file, port, log-line, or external-session condition uses the host's monitor when observed, else exactly ONE bounded watcher or adaptive backoff outside model turns. Record the handle and observation mode at dispatch; every armed wait needs a hard deadline, a cancellation path, and a fallback naming the missing capability. Each wait closes in one terminal state with bounded evidence; an unbounded idle or busy-wait is a defect and a lost notification times out. One decision-changing midpoint peek and any user-requested status check stay allowed; neither is the wait mechanism. Ladder and terminal states: shared rail.
72
73Handoff policy:
74
75Keep this as Hermes-facing orchestration guidance first. Prepare executor, connector, gateway, or host-runtime handoff only when the user accepts that next step and observed evidence can be recorded.
76
77Required inputs:
78
79- user request
80- target context
81- delivery or status expectation
82- known missing evidence
83
84Expected outputs:
85
86- command_task_card/v1
87- command_scope/v1
88- command_safety_gate/v1
89- command_result_manifest/v1 when observed
90- next action
91- prepared-vs-observed boundary
92
93Artifact expectations:
94
95- command_task_card/v1 metadata-only wrapper card when prepared
96- command_scope/v1 with command text, working directory, environment assumptions, timeout, and stop condition
97- command_safety_gate/v1 separating read-only, write/mutation, network, credential, and destructive-risk commands
98- command_result_manifest/v1 only when exit code, stdout/stderr, logs, or terminal transcript are observed
99
100Safety rules:
101
102- A command operator card is not terminal launch, shell execution, package-manager action, test run, stdout/stderr capture, exit-code success, filesystem mutation, network access, or destructive command evidence unless observed command-result evidence records it.
103- Do not claim connector, gateway, runtime, file generation, memory mutation, or host automation evidence from prepared guidance.
104
105## Runtime Evidence
106
107Preferred harness for this skill: `command-operator`.
108
109```sh
110omh runtime record --skill command-operator --harness command-operator --status started
111```
112
113Record observed delegation results; otherwise return `not_available` or `not_observed`.
114Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
115- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes.
116Preserve workflow intent and stop conditions; verify before claiming completion.
117
118Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
119
120Shared 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