crowsnest-reportlisted
Install: claude install-skill thorwhalen/crowsnest
# crowsnest-report — the page, and the loop it opens
A terminal roster is unreadable on a phone. `crowsnest report` renders the same rows as
one self-contained page; publishing it as an artifact turns that page into a two-way
channel, because the user can highlight a row, write an instruction, and send it to you.
## 1. Render
```bash
crowsnest report --fragment --interactive --out <file>.html # --fragment: the publisher wraps it; --interactive: the console
```
Four registers, in the order a person needs them: **Waiting on you**, **Just finished**,
**Working**, **Quiet**. The page is a snapshot — the generation time is in the largest
type on it.
Every session the page names leads to that session. A session running with Remote Control gets an **open** link to it on claude.ai. Any other session gets the `crowsnest open` command that reaches it from a terminal, shown as code, never as a link. **Who started whom** does the same in the list under its figure.
If the user only wanted something to read, hand over the path and stop here.
### A page you write by hand
When you write a page yourself rather than rendering one, every session you name on it is linked exactly as the rendered page links it, and from the same place:
- `crowsnest roster --json` (add `--all-homes` for every account): each row's `session_url` and `open_command`.
- `crowsnest show <address> --json`: the same two fields, under `session`.
When `session_url` is non-empty, link the session's name to it. Whe