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.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Diagnose first, change one thing at a time, verify after each change.
superset status for host service healthsuperset auth whoami for auth and the active orgsuperset hosts list for host reachabilitysuperset --version| 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 |
A host set up with superset hosts add is offline or broken | re-run superset hosts add <ssh-target>; it checks each step and fixes only what is wrong. On Linux its log is ssh <ssh-target> journalctl --user -u superset-host -n 50 |
hosts add cannot reach or set up the machine | confirm ssh <ssh-target> works from here, the remote is macOS or glibc Linux (x64 or arm64; Alpine and Windows are not supported), and it has curl |
Private repos will not clone on a host added with hosts add | sign in GitHub there: ssh -t <ssh-target> gh auth login (install gh first if missing) |
| Linux host stops when the user logs out of it | enable lingering on that machine: loginctl enable-linger |
hosts add stops on an empty or invalid /etc/machine-id (cloned VM or container image) | on that machine, sudo rm -f /etc/machine-id && sudo systemd-machine-id-setup, then re-run hosts add. The user runs this, since it needs sudo on their box |
superset pages publish in a Superset terminal fails with "Not a member of organization" | superset update; newer CLIs use the desktop app's account inside its terminals |
| 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".
Re-run the originally failing action. If it works, say exactly what was wrong and what fixed it.
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.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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, pages) 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.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a recurring chore into a Superset automation. Drafts the agent prompt, confirms the schedule or event trigger and the 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 an agent that reacts to a Slack message, GitHub pull request, Linear issue, Sentry issue or incoming email, or says things like "every morning do X", "automate this", "set up a cron agent", "run this on a schedule", "when someone opens a PR, do X".
日本語の概要は準備中です。原文の説明を表示しています。
Open, navigate, screenshot, read, click, and type in web pages from an agent. Use when the user asks to open a URL, preview or verify a running web app, check a page's console, fill a form, click through a web flow, or automate anything in a browser, including "open localhost:3000", "screenshot the page", "what does the console say", "click the submit button", "I'm logged in on Chrome". Drives the in-app browser pane of a Superset workspace by default and Browser Use for browsers the panes cannot reach.
日本語の概要は準備中です。原文の説明を表示しています。
Write Stripe code against what the API does today — plan the product shape, confirm every parameter from Stripe's own docs and schemas, and keep the agent in a sandbox. Use when adding checkout, billing, subscriptions, invoicing, or webhooks to a codebase, or when debugging Stripe integration code that compiles but behaves wrong.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose a failing GitHub Actions run — find the first real error in the logs, tell a flake apart from a genuine failure, and identify the commit that broke it. Use when checks are red on a PR, a workflow failed, the build is broken, CI is flaky, or the user asks why a run failed or whether a failure is real.
日本語の概要は準備中です。原文の説明を表示しています。