10x
Personalized audit that teaches the advanced Superset features the user isn't using yet (automations, parallel agents, tasks, multi-host, terminal remote control, custom commands, MCP) and sets them up live. Use when the user wants to get more out of Superset, asks "what else can Superset do", "how do I 10x my workflow", "what am I missing", or wants to learn a specific Superset feature.
git clone --depth 1 https://github.com/superset-sh/superset /tmp/10x && cp -r /tmp/10x/plugins/superset/skills/10x ~/.claude/skills/10xSKILL.md
# Superset 10x
Teach the user the advanced Superset features they aren't using yet, grounded in their real usage rather than a lecture. If they named a topic after the command, skip the audit and go straight to that topic.
## 1. Audit (read-only)
Run `bash scripts/audit.sh` from this skill's directory (`bash ${CLAUDE_SKILL_DIR}/scripts/audit.sh` in Claude Code). It runs `superset auth whoami`, `automations list`, `workspaces list`, `agents list --local`, `hosts list`, and `tasks list` with `--json`, tolerating individual failures, and prints one JSON object.
If the CLI is missing, offer to install it: `curl -fsSL https://superset.sh/cli/install.sh | sh`. If unauthenticated, `superset auth login`. If the audit is impossible, ask the user what their current workflow looks like and proceed from their answer.
## 2. Scorecard
Compare their usage against the catalog below and present a short scorecard: the 3-5 highest-impact features they aren't using, one line each on the payoff. No walls of text.
## 3. Walk through one at a time
For each recommendation in order: a two-sentence pitch, then ask (use the ask_user tool if available) with options **Set it up now** / **Tell me more** / **Skip**. "Set it up now" means actually doing it, creating the real automation or spawning the real workspace, after confirming the specifics (name, schedule, prompt) with the user. Never print instructions as a substitute for doing it.
## Catalog
| Feature | Why it 10x's you | Live setup |
| --- | --- | --- |
| Automations | Scheduled agents: triage, changelogs, standups run while you sleep | `superset automations create`, then `superset automations logs` to review runs |
| Parallel workspaces | Every task gets an isolated worktree; run several agents at once instead of queueing | `superset workspaces create --project <id>` then `superset agents create --workspace <id> --agent claude --prompt "..."` |
| PR review workspaces | Check out any PR into its own workspace in one command | `superset workspaces create --pr <number>` |
| Tasks | A shared queue agents can pick up; track work across sessions | `superset tasks create --title "..."`, `superset tasks update` |
| Multi-host | Run agents on your desktop from your laptop; wake offline machines | `superset hosts list`, `superset hosts set-wake`, `superset hosts wake <id>` |
| Terminal remote-control | Read and drive any agent's terminal from anywhere | `superset terminals list / read / send` |
| Custom slash commands | Your repo's own workflows as commands every agent can run | create `.agents/commands/<name>.md` in their repo |
| MCP servers | Give every workspace agent the same extra tools | add servers to `.mcp.json` at their repo root |
| Feedback loop | Report bugs or ideas without leaving the agent | the feedback skill |
## Rules
- The audit is read-only; never create, modify, or delete anything before the user picks "Set it up now" and confirms the specifics.
- One feature at a time; keep each step short and end it with the ask.
- Close with a one-line recap of what was set up and what they skipped, so they can come back and re-invoke this skill with a topic later.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.