automate
Turn a recurring chore into a Superset automation. Drafts the agent prompt, confirms schedule and target, creates it with the CLI, and reviews the first run together. Use when the user wants a scheduled or recurring agent, a daily or weekly job, or says things like "every morning do X", "automate this", "set up a cron agent", "run this on a schedule".
git clone --depth 1 https://github.com/superset-sh/superset /tmp/automate && cp -r /tmp/automate/plugins/superset/skills/automate ~/.claude/skills/automateSKILL.md
# 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. ## 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 ```bash 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.
Canonical three-section structure for Linear and Superset tickets in this repo. Use when creating, drafting, or grooming a ticket.
Validates project structure against co-location and architecture patterns defined in AGENTS.md
Create workspaces, spawn agents, schedule automations, and manage Superset projects/tasks/hosts via the `superset` CLI. Use to orchestrate coding agents across devices from the terminal.
Verify UI behavior end-to-end by driving the running desktop app over the Chrome DevTools Protocol. Use when asked to verify, reproduce, or confirm a UI change, bug, or regression in the real app rather than in tests.
Create a database migration with Drizzle on a fresh Neon branch. Use when changing the packages/db schema or generating migrations.
Walk the user through design or implementation decisions one at a time, or review completed code one change at a time. Use when the user says "walk me through each decision", "let's decide together", "help me work through these choices", "walk me through what you did", or "QA step by step". Present concise context, mutually exclusive options, log each answer, and finish with a summary.
Critique and improve the visual design of an existing UI component with concrete implementation guidance. Use when the user asks to redesign, restyle, reimagine, polish, or improve a component, screen, or interface, especially in React and Tailwind codebases.
Read and update the Superset desktop app's user settings (theme, fonts, terminal, git, notifications, behavior) via the superset CLI, including creating and installing custom themes from JSON. Use when asked to change app settings, switch or create a theme, adjust fonts, or configure desktop preferences without opening the settings UI.