superset-sh Superset Automate
Turn "I keep doing X every morning" into an automation that does X on a schedule.
1. Understand the chore
Pin down: the outcome, the cadence, the inputs it reads, and what "done" looks like. Then draft the automation prompt as instructions for an agent with zero context. If the task has rules that will evolve (triage criteria, formats), put them in a document the automation reads at runtime so they can be edited without touching the prompt.
Nobody watches a run, so a chore whose product is a digest, a report, or a scorecard needs somewhere for that product to land. End the prompt by writing the report to an .html file and publishing it, so the user opens one link instead of digging through run logs.
...write the digest to digest.html, then publish it:
superset pages publish digest.html --title "Nightly triage" --label "what changed today"
A page is identified by its workspace plus its path, so which target you picked in step 2 decides whether history accumulates. A project target creates a fresh workspace per run, which means a new page every run rather than a new version of one. For a report meant to build up history, use a workspace target, or capture the page id from the first run and have the prompt pass --page <id> from then on.
2. Pick the target
superset projects list: a project target creates a fresh workspace per run (most tasks)superset workspaces list: a workspace target reuses the same workspace every run (stateful tasks)
3. Confirm before creating
Show the user (use the ask_user tool if available): the name, the schedule as an RRULE, the agent, the target, and the exact command you will run. Never create without explicit confirmation.
4. Create and shake down
superset automations create \
--name "Daily issue triage" \
--rrule "FREQ=DAILY;BYHOUR=9;BYMINUTE=0" \
--timezone America/Los_Angeles \
--project <id> \
--agent claude \
--prompt-file /tmp/automation-prompt.md
(--workspace <id> instead of --project for reuse mode; --host <id> if it should run on another machine; prefer --prompt-file for multiline prompts.)
Then trigger a first run now with superset automations run <id>, review superset automations logs <id> with the user, and refine the prompt via superset automations prompt set <id> until the run output is right. An automation isn't done until one real run looked good. If the prompt publishes a page, open the published page as part of that review, not just the run log.