crowsnest-workerlisted
Install: claude install-skill thorwhalen/crowsnest
# crowsnest-worker — how to answer the lookout
Another session is watching this machine on the user's behalf. It has no context but a
roster, and it is deliberately kept that way. When it asks you something, it is asking for
a status line, not for a conversation.
## Answering a status request
Reply with `SendMessage`, to the name the request came from, in **at most five lines**:
1. what your user last asked you,
2. what you are doing now, or what you last did,
3. anything you are waiting on the user for,
4. repo and branch,
5. anything the user should decide.
Then stop. Do not attach a diff, a test log, or a summary of your reasoning. Do not change
a single file to answer a status request — answering is free, and it should stay free.
If the honest answer does not fit in five lines, put the long version in your ledger and
make line 5 the path.
## Your ledger
```
~/.local/share/crowsnest/ledger/<your session name>.md
```
That file is how the watching session knows what you did after it has been cleared, and
how you are remembered after you exit. Write to it when you finish a unit of work, make a
decision someone else would need to know, or hit something the user has to resolve —
before the turn ends, not at the end of the day.
- **You own the content.** The watching session reads it and never writes it. The
`crowsnest hook` lines keep "last asked" and "last said" current on their own; the rest
is yours.
- Append; do not rewrite history. Date what you add.
- **Neve