scheduleslisted
Install: claude install-skill specstream/specstream-tools
# Keep a list current on a schedule
SpecStream is the live web data engine for teams and agents. Use the configured MCP server at `https://api.specstream.ai/mcp`.
A schedule (a monitor) reruns a request on the live web at a set cadence and labels each record: still matches, no longer matches, unresolved or unavailable. A refresh costs half the row rate for a row that changed and 1 cent for a row that did not.
## Set it up
1. Read the request with `compile` and show the person how it was read. Price it with `quote_capacity_work`.
2. Agree on the cadence and the limits with the person before any write: how often it runs (`cadence_seconds`, at least 3600, or a `calendar_schedule`), the first run (`first_due_at`), the end date (`valid_until`), the most one run can spend (`per_run_cents`) and the most it can spend in one UTC calendar month (`period_cents`).
3. `create_capacity_schedule` is a write. Call it only after the person says yes to those limits, with the priced scope and a stable `idempotency_key`. The response shows `monthly_maximum_cents` and `scheduled_monthly_cents`; show both to the person.
Creating a schedule does not fund it. A balance or a schedule is never permission to spend more than the agreed limits. A blocked or missed run is not an unchanged result and is not bought later.
## Deliver to a webhook
`set_schedule_delivery` chooses where new and changed records go: `notify` (SpecStream notifications), `slack` (a channel of the one connected Slack workspac