harness-clilisted
Install: claude install-skill on-keyday/agent-harness
# harness-cli (agent runtime)
`harness-cli` is on `PATH` inside this worktree. It is your control surface for
the whole harness. This skill covers the half you need to talk to other agents:
the agentboard (the only sanctioned way to do so), plus operator notifications
(`notify`). The half about driving OTHER agents — spawning worker sessions,
`--caps`, one-shot `submit` + `logs` / `watch`, `file push` / `file pull`, and
reading a worker's diff — is the `supervising-workers` skill. All required
credentials are passed via `HARNESS_*` environment variables (already set by
the runner) — never pass them as flags.
## Reading the skills — `harness-cli skill`
This document, and the other harness agent skills, are embedded in the
`harness-cli` binary. Print them from any runtime — you do NOT need Claude's
skill mechanism, and this works even where `.claude/skills/` was never injected:
```bash
harness-cli skill # print this skill (harness-cli) — the default
harness-cli skill ls # list the embedded skills + descriptions (alias: --list / -l)
harness-cli skill <name> # print another one, e.g. `harness-cli skill landing-to-main`
```
`harness-cli version` reports the commit this binary was built from, which is
also the version of every skill it PRINTS — they are embedded in it. It does
not describe the copies on disk under `.claude/skills/` and `.agents/skills/`:
the runner writes those at spawn time out of its own binary, so their vintage
comes from a different