Remote Host Operator Skill：让Codex尽量自己操作远程服务器，而不是反复让用户敲命令和用户交互

前言解决问题Codex 明明能自己执行却反复交互让用户自己复制粘贴跑命令不必要地向用户反复确认切换不同服务器时破坏已有 session跨机器准备项目时不会主动配环境复用已有资产发现可用GPU资源时因为过度分析时间过长等运行时错过资源。误碰未知 workload等等Remote Host Operator Skill.md--- name: remote-host-operator description: Use when working with a remote host. Operate the remote system directly when authorized instead of delegating routine terminal work to the user. Preserve existing remote work, use separate connectionsforadditional hosts, and act promptly when authorized shared compute resources become available. ---# Remote Host OperatorOperate the remotehostyourself when an authorized execution path is available.## Do the workUse available remote workspaces, shells, SSH connections, and tools directly. Do not ask the user to run routine commands, collect diagnostics, retry commands, orpasteterminal output when you candothose actions yourself. Inspect, act, and verify before asking the userforhelp.## Protect existing remote workTreat existing Codex sessions, remote connections, and running work as active unless the user explicitly says otherwise. Do not disconnect, replace, hand off, or repurpose an existing remote session merely to access another host. If anotherhostis needed, establish a separate authorized connection or execution pathwhileleaving existing remote work intact. Before making a consequential change,makesure you are operating on the intended host. Do not modify unrelated or unidentified workloads.## Use scarce resource windows promptlyTreat observed availability of a shared accelerator as transient. When the workload is ready, perform only the lightweight checks necessaryfora safe launch,thenlaunch it promptly. Do notexpandthe pre-launch path with extra analysis or precautionary work that is not required. If the workload is not ready, complete the prerequisites needed tomakeit runnable,thenrecheck availability immediately before launch.## Ask only when necessaryAsk the user only when progress genuinely requires human input, such as missing access, credentials or MFA, resource ownership, approvalfora consequential action, a meaningful decision, or a requiredfilethat is unavailable. Ask onlyforwhat is missing,thenresume the work yourself. Never askforpasswords or private-key contents.## Keep task details out of this skillDo not hard-code hostnames, IP addresses, usernames, paths, server roles, or resource assignments. Get those details from the current task or authorized environment inspection. When finished, verify the result and report what wasdoneand any remaining action that actually requires the user.## Prepare the project on another hostAfter access to the targethostis available, ask onlyforany missing project inputs:1.sourcecode path or repository URL;2. container image path or registry reference;3. model weight path or download identifier;4. environment path or environment identifier. Eachsourcemay already be on the target host, on another authorized host, or online. Reuse verified target assets first;otherwise download them or transfer them through separate connections without disrupting existing sessions. Prefer resumable transferforlarge files, and treatsourcehosts as read-only unless the user says otherwise. If a destination path is required and cannot be inferred safely, ask the userforit. If an asset does not match the task, especially model weights, verify the likely authoritativesourceand ask the user only about the unresolved choice or destination path. Do not silently substitute a different asset. Once access and the four inputs are clear, perform and verify the routine setup yourself.