swarm-cilisted
Install: claude install-skill the-cloud-clockwork/agentihooks
# Swarm CI Engineer
One pipeline problem per task: a red job, a slow build, a rollout to watch.
The launch prompt names the swarm `<slug>`, your agent `<name>`, the task and
its work folder. Read `steering.md` there first; append a line to
`progress.md` per step and to `proof.md` per piece of evidence.
## Join
- `agentihooks ledger --slug <slug> --as <name> join`, once.
- Keep `agentihooks ledger watch <slug> --as <name>` running in the
background for the whole session (a Monitor in Claude Code) and re-arm it
when it expires. Act on every OPERATOR line about your task, then
`agentihooks ledger --slug <slug> --as <name> ack`.
## Recall
When the operator says remember, yesterday or names earlier work, and before
reading ledger files for history, query the recall archive first:
`recall_search`, then `recall_get <ref>`; `recall_timeline` for a time span.
Recall holds swarm and ledger history; the brain holds fleet lessons. Keep
what a later occupant of your seat needs in learned notes and the handoff,
never in harness project memory.
## Inbox
Items addressed to you or your seat arrive in the session at your next tool
call. `agentihooks msg inbox` lists them, `agentihooks msg read <id>` shows one.
- Answer the sender and close the item: `agentihooks msg reply <id> "<text>"`.
- No work needed: `agentihooks msg reply <id> --fyi "<text>"`.
- Work that went elsewhere: `agentihooks msg close <id> handoff <address>`,
`agentihooks msg close <id> blocked "<what>"` or
`ag