executor-runtime-readiness
starsforks
How to install executor-runtime-readiness?
rlaope/oh-my-hermes/executor-runtime-readiness
$npx -y skills add rlaope/oh-my-hermes --skill executor-runtime-readiness[omh] Hermes executor runtime readiness workflow: compare Codex, Claude Code, Hermes coding, and oh-my runtimes by available tools, missing tools, and handoff mode.
SKILL.md
| 1 | # Executor Runtime Readiness |
| 2 | |
| 3 | This is a Hermes-native `executor-runtime-readiness` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `executor-runtime-readiness` 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: executor-runtime-readiness can this task run in Codex, Claude Code, or Hermes coding? |
| 20 | - Expected behavior: Produce `prepare_executor_runtime_readiness` 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: executor-runtime-readiness claim Codex already started the session. |
| 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 | - The selected coding or runtime owner is named before any implementation claim. |
| 32 | - Prepared handoff, dispatch, execution, verification, review, CI, and merge states are separated. |
| 33 | - The final status cites observed runtime evidence or keeps the work prepared_not_observed. |
| 34 | - When Hermes is the selected coding owner, use `hermes_coding_harness/v1` to keep builder, verifier, reviewer, docs, and PR lanes separate. |
| 35 | - Report the current harness stage, owner, next action, and missing evidence without claiming PR creation, review, CI, merge-readiness, or merge until matching runtime observations exist. |
| 36 | |
| 37 | ## Recovery Notes |
| 38 | |
| 39 | - If the selected executor is unavailable, ask for Codex, Claude Code, Hermes, or another runtime before retrying. |
| 40 | - If dispatch or result evidence is missing, keep the handoff prepared_not_observed and expose the next observable action. |
| 41 | |
| 42 | ## OMH Context Rail |
| 43 | |
| 44 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 45 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 46 | - Current lane: **Coding handoff** (`idea-to-deploy`, `cto-loop`, `deploy-and-monitor`, `code-review`, `build-failure-triage`, `verification-gate`, `security-safety-review`, `ultrawork`, `+7 more`) - coding owners, handoffs, review, CI, and merge evidence. |
| 47 | - 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. |
| 48 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 49 | - 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. |
| 50 | - Coverage: Every generated workflow skill carries this rail. |
| 51 | - Normal users talk to Hermes; OMH CLI is infra. |
| 52 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 53 | |
| 54 | ## Use When |
| 55 | |
| 56 | Use when a user may choose Codex, Claude Code, Hermes coding, or another runtime and needs tool/credential gaps before handoff. |
| 57 | |
| 58 | Strong routing signals: `executor-runtime-readiness`, `executor readiness`, `runtime readiness`, `codex readiness`, `claude code readiness`, `hermes coding readiness`, `executor tools`, `missing tools`, `missing runtime tools`, `runtime tools`, `coding agent readiness`, `coding runtime`, `handoff mode`, `handoff readiness`, `codex or claude`, `codex vs claude`, `codex tools`, `claude code tools`, `hermes coding`, `agent runtime`, `subagent readiness`, `worktree readiness`, `codex로 넘길지 claude`, `claude code로 넘길지 codex`, `codex랑 claude`, `claude code 중`, `넘길지 codex`, `넘길지 claude`, `runtime migration`, `omx`, `omc`, `omo`, `코덱스`, `클로드 코드`, `헤르메스 코딩`, `코딩 에이전트`, `서브에이전트`, `작업트리`, `준비성`, `실행 런타임`, `어떤 런타임`, `런타임으로 넘겨` |
| 59 | |
| 60 | ## Catalog Metadata |
| 61 | |
| 62 | Category: `executor-readiness` |
| 63 | Phase: `runtime-selection` |
| 64 | Hermes role: `handoff-guide` |
| 65 | Quality tier: `workflo |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
