command-operator
starsforks
How to install command-operator?
rlaope/oh-my-hermes/command-operator
$npx -y skills add rlaope/oh-my-hermes --skill command-operator[omh] Hermes command operator workflow: scope terminal, shell, CLI, package-manager, and test commands with cwd, environment, safety, and result-evidence gates.
SKILL.md
| 1 | # Command Operator |
| 2 | |
| 3 | This is a Hermes-native `command-operator` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `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. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The request is already handled by a narrower explicit skill with stronger evidence. |
| 12 | - The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents. |
| 13 | - The only safe answer is to ask for missing authority, credentials, target, or observed evidence first. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: command-operator run npm test in the project terminal and summarize the output. |
| 20 | - Expected behavior: Produce `prepare_command_operator_card` with required context, wrapper actions, and not-evidence boundaries. |
| 21 | - Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: command-operator run rm -rf without cwd, confirmation, or observation gates. |
| 26 | - Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened. |
| 27 | - Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence. |
| 28 | |
| 29 | ## Completion Checklist |
| 30 | |
| 31 | - Command text, working directory, environment assumptions, timeout, safety level, and stop condition are explicit. |
| 32 | - Destructive, credential, network, filesystem mutation, install, deploy, and production commands are gated or marked missing. |
| 33 | - Exit codes, stdout/stderr, test results, package-manager effects, and filesystem mutations are reported only from observed command evidence. |
| 34 | |
| 35 | ## Recovery Notes |
| 36 | |
| 37 | - If command text or working directory is missing, ask for the smallest missing scope needed before preparing the command task. |
| 38 | - If the command is destructive, credentialed, networked, install/deploy-oriented, or production-affecting, require an explicit confirmation gate. |
| 39 | - 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. |
| 40 | |
| 41 | ## OMH Context Rail |
| 42 | |
| 43 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 44 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 45 | - Current lane: **Automation and status** (`achievements`, `workspace-audit`, `production-audit`, `automation-blueprint`, `github-event-ops`, `agent-board`, `gateway-intent-card`, `voice-operator`, `+26 more`) - schedules, status, health, and ops review. |
| 46 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 47 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 48 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 49 | - Coverage: Every generated workflow skill carries this rail. |
| 50 | - Normal users talk to Hermes; OMH CLI is infra. |
| 51 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 52 | |
| 53 | ## Use When |
| 54 | |
| 55 | Use when Hermes should prepare or supervise terminal/CLI command execution without claiming the command ran or succeeded. |
| 56 | |
| 57 | 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 실행`, `테스트 실행`, `결과 요약` |
| 58 | |
| 59 | ## Catalog Metadata |
| 60 | |
| 61 | Category: `command` |
| 62 | Phase: `command-task` |
| 63 | Hermes role: `guide` |
| 64 | Quality tier: `workflow-surface-gated` |
| 65 | |
| 66 | Quality 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 | |
| 72 | Handoff policy: |
| 73 | |
| 74 | Keep thi |
People who liked this also viewed
6 picksType
- paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hSkillsJul 2026
- subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionSkillsJul 2026
- dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillsJul 2026
- browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a sitSkillsJul 2026
- wizardGenerate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each stSkillsJul 2026
- wonda-cliUsing the Wonda CLI to generate images, videos, music, and audio from the terminal — plus LinkedIn, Reddit, and X/Twitter research and automationSkillsJul 2026
