omh-command-operator

# 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 ...