/10x
Personalized audit that teaches advanced Superset features the user isn't using yet — automations, parallel agents, tasks, multi-host, terminals, custom commands, MCP. Use when the user wants to get more out of Superset, learn advanced Superset features, or 10x their Superset
$ npx -y skills add superset-sh/superset --skill 10x --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/10x
Context preview
The summary Claude sees to decide when to auto-load this skill.
Personalized audit that teaches advanced Superset features the user isn't using yet — automations, parallel agents, tasks, multi-host, terminals, custom commands, MCP. Use when the user wants to get more out of Superset, learn advanced Superset features, or 10x their Superset
SKILL.md
10x.SKILL.mdname: 10x
description: Personalized audit that teaches advanced Superset features the user isn't using yet — automations, parallel agents, tasks, multi-host, terminals, custom commands, MCP. Use when the user wants to get more out of Superset, learn advanced Superset features, or 10x their Superset workflow.
argument-hint: optional topic, e.g. automations
Superset 10x
Teach the user the advanced Superset features they aren't using yet — grounded in their real usage, not a lecture. If they named a topic after the command, skip the audit and go straight to that topic.
1. Audit (read-only)
Run in parallel and tolerate individual failures (prefer `--json` where supported):
- `superset auth whoami`
- `superset automations list`
- `superset workspaces list`
- `superset agents list`
- `superset hosts list`
- `superset tasks list`
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 — create the real automation, spawn 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 | invoke the `feedback` skill from this plugin |
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.
Read more
name: 10x description: Personalized audit that teaches advanced Superset features the user isn't using yet — automations, parallel agents, tasks, multi-host, terminals, custom commands, MCP. Use when the user wants to get more out of Superset, learn advanced Superset features, or 10x their Superset workflow. argument-hint: optional topic, e.g. automations
Superset 10x
Teach the user the advanced Superset features they aren't using yet — grounded in their real usage, not a lecture. If they named a topic after the command, skip the audit and go straight to that topic.
1. Audit (read-only)
Run in parallel and tolerate individual failures (prefer `--json` where supported):
- `superset auth whoami`
- `superset automations list`
- `superset workspaces list`
- `superset agents list`
- `superset hosts list`
- `superset tasks list`
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 — create the real automation, spawn 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 | invoke the `feedback` skill from this plugin |
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.
Code Editor for the AI Agents Era - Run an army of Claude Code, Codex, etc. on your machine
Other skills on superset.
- /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/weekly job, or to automate a repeating task
Open skill - /contribute
Set up a Superset open-source contribution — fork and clone superset-sh/superset, run local dev setup, and follow the repo's contribution rules through to a merge-ready PR. Use when the user wants to contribute to Superset, fix a Superset bug themselves, or prepare a PR against
Open skill - /doctor
Diagnose and fix Superset problems — connection failures, offline hosts, terminals not attaching, auth or update issues. Use when the user reports something broken or misbehaving in Superset itself, before filing feedback.
Open skill - /feedback
Collect and submit feedback about Superset — bug reports, feature requests, or general feedback — privately to the Superset team or as a public GitHub issue. Use when the user wants to report a Superset bug, request a feature, or send feedback about Superset.
Open skill - /orchestrate
Coordinate multiple terminal coding agents through the Superset CLI by creating isolated workspaces, launching workers, sending follow-ups, reading terminal output, tracking dependencies, and collecting structured results. Use when asked to delegate or parallelize coding work,
Open skill - /setup
Make a repository Superset-ready — author .superset/config.json with setup/teardown/run scripts so every new workspace boots configured, then verify with a real workspace. Use when the user wants to set up a project or repo for Superset, configure workspace setup scripts, or fix
Open skill

