Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →superset-sh/superset-orchestration
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.
Passed 15 of 19 test cases with the skill, and 3 of 19 without it.
and 13 more in the full report
13 fixed4 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to read recent terminal output from worker session `term-abc` in workspace `ws-12` using Superset CLI. Show the command to inspect log history up to 240 lines in JSON format.
| Checked | Without skill | With skill |
|---|---|---|
| Includes --max-lines 240 in the superset terminals read command | Missed | Passed |
The instructions your model reads when the skill loads.
Coordinate terminal agents with Superset's workspace, agent, and terminal commands. Treat this as a coordinator-driven protocol: Superset provides session transport, while the coordinator owns task dependencies and completion state.
superset auth whoami --json.superset terminals --help and require list, read, send, and close.superset update and recheck. Do not invent or substitute unsupported orchestration commands.bun run --cwd packages/cli dev -- in place of superset to exercise the source CLI against the API configured in the root .env. To reuse production CLI authentication while testing unreleased source commands, run them from packages/cli with SUPERSET_API_URL=https://api.superset.sh bunx cli-framework dev.superset hosts list --json
superset agents list --local --json
superset workspaces list --local --json
When coordinating from inside the target workspace, pass --workspace "$SUPERSET_WORKSPACE_ID" explicitly to agent and terminal commands. Only workspaces get defaults its workspace ID from that environment variable. Pass --host <id> consistently for a remote host. If the target host is offline, use hosts wake <id> and confirm it is online before dispatching. Do not use --agent superset: it creates a chat session, and terminal read/send cannot control it.
Create a compact coordinator table with these fields:
| Field | Purpose |
|---|---|
| Task | Stable short identifier |
| Dependencies | Tasks that must complete first |
| Workspace | Superset workspace ID |
| Host | Host ID, or local |
| Terminal | sessionId returned by agents create |
| Status | pending, ready, running, completed, blocked, or failed |
| Result | Summary, files, checks, and follow-up work |
Keep this state in the coordinator's working context. Superset organization tasks are issue-tracker records, not orchestration DAG nodes; do not create or mutate them unless the user asks.
Prefer independent tasks and shallow dependency chains. For parallel editing, give workers separate workspaces/branches. Sharing one workspace is appropriate for read-only analysis or deliberately complementary work with non-overlapping files.
test cases passed, vs 3 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.