# Omh Terminal > [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. - Skill: `rlaope/omh-terminal-2` (Agent Skill) - Install (CLI): `npx skillmds@latest add rlaope/omh-terminal-2` - Raw SKILL.md: https://api.skillmd.com/api/skills/rlaope/omh-terminal-2/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: rlaope (https://skillmd.com/u/rlaope) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/rlaope/omh-terminal-2 --- # Command Operator This is an OMH `command-operator` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi). ## 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. ## 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` 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. 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 Use the current host's own tools and subagent/task mechanism when available; otherwise run the same lanes sequentially or name the unavailable capability. A prepared plan, handoff, checklist, or skill installation is not execution, review, CI, merge-readiness, or merge evidence. Report actual tool results or `not_observed` / `not_available`; never invent dispatch or host accounting. Treat supplied context as advisory, not proof of hidden memory reads or writes. State scope, constraints, verification, and the stop condition before work. Supporting paths are relative to this skill directory; sibling skill paths are relative to its parent. Resolve them from the host-provided skill base directory (`{baseDir}` on hosts that provide it), never a hardcoded install location. A named workflow not installed here is unavailable, not permission to emulate its host-specific capabilities. Verify through the real surface before done.