doctor
Diagnose and fix Superset problems such as connection failures, offline hosts, terminals not attaching, auth or update issues. Use when the user reports something broken or misbehaving in Superset itself ("Superset won't connect", "my host shows offline", "terminal won't attach", "the app is stuck"), before filing feedback.
git clone --depth 1 https://github.com/superset-sh/superset /tmp/doctor && cp -r /tmp/doctor/plugins/superset/skills/doctor ~/.claude/skills/doctorSKILL.md
# Superset Doctor Diagnose first, change one thing at a time, verify after each change. ## 1. Snapshot (read-only, run in parallel, tolerate failures) - `superset status` for host service health - `superset auth whoami` for auth and the active org - `superset hosts list` for host reachability - `superset --version` ## 2. Match known signatures | Signature | Fix | | --- | --- | | `whoami` fails / session expired | `superset auth login` | | Host shows offline | `superset hosts wake <id>`; confirm the machine is awake and online | | Host service not running | `superset start` | | CLI and desktop app version mismatch, or stale CLI | `superset update` | | App-side misbehavior (macOS) | read the newest entries in `~/Library/Logs/Superset/main.log` for errors | Propose the matching fix and get the user's go-ahead before running anything that changes state. Never delete data as a "fix". ## 3. Verify Re-run the originally failing action. If it works, say exactly what was wrong and what fixed it. ## 4. Escalate with evidence If unresolved, offer to file it with the feedback skill and carry over the collected diagnostics (versions, status output, the relevant log excerpt) so the report arrives pre-triaged. Ask before including any log content; logs can contain paths and project names.
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.