菜单
Use as the entry skill for Workhorse `cargo work` tasks. It classifies the request first, then routes to the right sub-skill for remote Rust builds, remote shell or proxy access, or artifact retrieval, Git sync, and server inspection on a `horsed` server.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | workhorse-cargo-work |
| description | Use as the entry skill for Workhorse `cargo work` tasks. It classifies the request first, then routes to the right sub-skill for remote Rust builds, remote shell or proxy access, or artifact retrieval, Git sync, and server inspection on a `horsed` server. |
This is the dispatcher skill for the cargo-work side of Workhorse. Use it when a request mentions cargo work, horsed, remote Rust builds, remote command execution, artifact download, or Workhorse server inspection, and decide which specialized skill should take over.
Route to exactly one primary sub-skill whenever possible:
$workhorse-remote-build for remote build, test, check, clippy, run, install, doc, metadata, rustc, zigbuild, or just.$workhorse-remote-access for cargo work -- ..., cargo work exec, cargo work ssh, interactive shells, PTY-backed commands, port forwarding, remote env injection, or proxy bridging.$workhorse-artifact-sync for get, scp, push, pull, ping, health, logs, or job.--repo-name, --repo, Git remote horsed, or HORSED.$workhorse-remote-build and then switch to $workhorse-artifact-sync.$workhorse-remote-access.cargo test" -> $workhorse-remote-build$workhorse-remote-access$workhorse-remote-access$workhorse-remote-access$workhorse-artifact-sync$workhorse-artifact-sync$workhorse-artifact-sync--repo nor a horsed Git remote can identify the target.~/.ssh/id_rsa or ~/.ssh/id_ed25519 unless --ssh-key is provided.cargo work ping without --count keeps running; use plain cargo work or cargo work ping --count <n> for finite connectivity checks.cargo work watch exists but is not reliable enough to recommend as a default workflow.Use when the user wants remote shell access or ad-hoc command execution through `cargo work`, including raw `cargo work -- ...` commands, stdin script execution with `cargo work exec`, `cargo work ssh`, port forwarding with `-L` or `-R`, environment injection, PTY allocation, shell selection, and reverse proxy setup with `-x` or `--all-proxy`.
Use as the top-level entry skill for this repository. It classifies Workhorse requests first, then routes to the right dispatcher for `cargo work` client tasks or `horsed` server tasks, including remote builds, remote access, artifact sync, server setup, operations, and `horsed` development.
Use when the user wants to fetch files or build outputs from a `horsed` server with `cargo work get` or `scp`, sync Git state with `cargo work push` or `pull`, inspect server status with `cargo work ping`, `health`, and `logs`, or inspect and attach running job output with `cargo work job`.
Use when the user wants to operate a running `horsed` server, wire it into `systemd`, `launchd`, or Windows Task Scheduler, inspect logs and health, choose between foreground and daemon modes, or troubleshoot runtime problems around ports, file descriptors, working directory, and setup mode.
Use when the user wants to run Rust build workflows on a `horsed` server via `cargo work`, including remote `build`, `test`, `check`, `clippy`, `run`, `install`, `doc`, `metadata`, `rustc`, `zigbuild`, and `just` commands, with target selection through `--repo`, `--repo-name`, or `--remote`.
Use when the user wants to modify the `horsed` server implementation itself, including SSH server behavior, setup flow, logging, IPC, SQLite schema, migrations, service startup logic, or server-side tests.