菜单
Use as the entry skill for `horsed` server tasks. It classifies the request first, then routes to the right sub-skill for first-time server setup, runtime operations and autostart, or `horsed` code, schema, and protocol development.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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 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.
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`.
| name | workhorse-horsed |
| description | Use as the entry skill for `horsed` server tasks. It classifies the request first, then routes to the right sub-skill for first-time server setup, runtime operations and autostart, or `horsed` code, schema, and protocol development. |
This is the dispatcher skill for the horsed side of Workhorse. Use it when a request mentions horsed, server bootstrap, setup mode on 2223, daemon or foreground behavior, autostart, logs, health, or changes to the horsed server implementation.
Route to one primary sub-skill whenever possible:
$workhorse-horsed-setup for first-time bootstrap, safe startup mode, setup server behavior on 2223, first-user enrollment, horsed.key, horsed.db3, and --dangerous.$workhorse-horsed-ops for day-2 operation, logs, health, autostart templates, service managers, runtime troubleshooting, and admin command behavior.$workhorse-horsed-dev for server code changes in horsed/src, migrations, logging internals, IPC, SSH action dispatch, or tests.horsed process itself or about cargo work on the client side.$workhorse-horsed-setup and then hand off to $workhorse-horsed-ops.$workhorse-horsed-ops for symptom framing and then hand off to $workhorse-horsed-dev.cargo-work dispatcher instead.horsed 首次启动起来" -> $workhorse-horsed-setup$workhorse-horsed-ops$workhorse-horsed-opshorsed 的 setup 逻辑" -> $workhorse-horsed-dev$workhorse-horsed-devhorsed writes state into its working directory.2222; setup mode is on 2223.horsed daemonizes by default; supervised environments generally want horsed -f.workhorse-horsed and workhorse-cargo-work instead of mixing both domains in one skill body.