aulalisted
Install: claude install-skill sorenlouv/aula-cli
# Aula
Read-only CLI over Aula's internal API. The read commands print JSON by default;
add `--text` for a human-readable rendering. The commands that manage the
installation itself — `open`, `publish`, `calendars`, `remember`, `preferences`,
`forget`, `schedule`, `login`, `logout`, `refresh-stepup` — already print text
and reject `--text`.
{{AULA_CLI_LOCATION}}
```bash
aula <command>
```
## Hard rule: read-only
This tool can only read. Never attempt to send a message, reply, create a post,
answer a calendar invitation, or mark anything as read — the client refuses
those calls in its transport layer anyway. When something needs a reply, tell
the user what it is and let them answer in Aula themselves.
## Start here
If you don't yet know the family, run `whoami` once — it lists the children,
their institutions, and which vendor widgets the schools expose.
For almost any open question ("what have I missed?", "anything important?",
"what's happening this week?") run one command:
```bash
aula digest --days 14
```
`digest` returns threads (with full message bodies), posts, upcoming calendar
events, presence and weekly plans in a single payload. Widen with `--days 30`
when the user asks about a longer period or 14 days comes back thin.
The `attention` block pre-computes the signals Aula itself exposes
(`unreadThreads`, `importantPosts`, `eventsAwaitingResponse`, …). Use it as a
starting point, **not** as the answer — Aula's own flags are weak signals, and
ranking what act