How do I install the Standup skill?

Run npx skillmds@latest add superset-sh/standup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Standup safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Standup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Standup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Standup?

superset-sh (@superset-sh) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Standup by superset-sh — Agent Skill

Name: Standup
Rating: 4.2 (5 reviews)
Author: superset-sh

Standup

Digest of what the user's Superset agents did while they were away, sweeping workspaces, tasks, and agent terminals to report what finished, what needs review, and what's blocked. Use when the user asks "what did my agents do", "what happened while I was away", wants a standup or summary of agent work, or returns after a break.

superset-sh Updated Sep 9, 2026

File contents

Superset Standup

Answer "what happened while I was away?" from real state, not guesses. Entirely read-only.

1. Sweep

Run bash scripts/sweep.sh from this skill's directory (bash ${CLAUDE_SKILL_DIR}/scripts/sweep.sh in Claude Code). It lists workspaces and tasks, then for each workspace lists its terminals and reads the last screen of every agent terminal, tolerating individual failures. Pass --host <id> to sweep a remote host, --max-lines <n> to change the per-terminal tail (default 60).

If the script can't run (no bash, no jq), do the same by hand: superset workspaces list --json, superset tasks list --json, then per workspace superset terminals list --workspace <id> --json and superset terminals read --workspace <id> --terminal <terminalId> --max-lines 60.

The last screen of a terminal shows whether the agent finished, asked a question, or errored.

2. Classify each workspace

Needs you: agent finished and awaits review, asked a question, or hit a permission prompt or failure
In flight: actively working
Blocked: waiting on something external
Stale: idle with no pending work, a candidate for cleanup

3. Report

Lead with what needs the user, one line per item: workspace, agent, state, and the next action. Then in-flight, then completed, then stale-workspace cleanup suggestions. Keep the whole digest scannable: no terminal dumps, quote at most the single relevant line an agent printed.

Offer the digest as a page when someone other than the user will read it, or when they want it to persist past the scrollback. Write the report you just composed to an .html file inside a workspace, then publish that file: the CLI publishes a document, not your terminal output.

superset pages publish standup.html --workspace <id> --title "Standup" --label "what shipped overnight"

Publishing the same file from the same workspace each morning versions one page instead of scattering a new one daily, so the history becomes the record of the week. A digest often runs from outside any workspace, and a publish with no workspace is refused, so pass --workspace explicitly. Offer it; never publish one unasked.

Rules

Never send input to a terminal, modify tasks, or clean anything up as part of the digest. Offer those as follow-ups and act only when asked.

---name: standupdescription: Digest of what the user's Superset agents did while they were away, sweeping workspaces, tasks, and agent terminals to report what finished, what needs review, and what's blocked. Use when the user asks "what did my agents do", "what happened while I was away", wants a standup or summary of agent work, or returns after a break.--- # Superset Standup Answer "what happened while I was away?" from real state, not guesses. Entirely read-only. ## 1. Sweep Run `bash scripts/sweep.sh` from this skill's directory (`bash ${CLAUDE_SKILL_DIR}/scripts/sweep.sh` in Claude Code). It lists workspaces and tasks, then for each workspace lists its terminals and reads the last screen of every agent terminal, tolerating individual failures. Pass `--host <id>` to sweep a remote host, `--max-lines <n>` to change the per-terminal tail (default 60). If the script can't run (no bash, no `jq`), do the same by hand: `superset workspaces list --json`, `superset tasks list --json`, then per workspace `superset terminals list --workspace <id> --json` and `superset terminals read --workspace <id> --terminal <terminalId> --max-lines 60`. The last screen of a terminal shows whether the agent finished, asked a question, or errored. ## 2. Classify each workspace - **Needs you**: agent finished and awaits review, asked a question, or hit a permission prompt or failure - **In flight**: actively working - **Blocked**: waiting on something external - **Stale**: idle with no pending work, a candidate for cleanup ## 3. Report Lead with what needs the user, one line per item: workspace, agent, state, and the next action. Then in-flight, then completed, then stale-workspace cleanup suggestions. Keep the whole digest scannable: no terminal dumps, quote at most the single relevant line an agent printed. Offer the digest as a page when someone other than the user will read it, or when they want it to persist past the scrollback. Write the report you just composed to an `.html` file inside a workspace, then publish that file: the CLI publishes a document, not your terminal output. ```bash superset pages publish standup.html --workspace <id> --title "Standup" --label "what shipped overnight" ``` Publishing the same file from the same workspace each morning versions one page instead of scattering a new one daily, so the history becomes the record of the week. A digest often runs from outside any workspace, and a publish with no workspace is refused, so pass `--workspace` explicitly. Offer it; never publish one unasked. ## Rules Never send input to a terminal, modify tasks, or clean anything up as part of the digest. Offer those as follow-ups and act only when asked.

Frequently asked questions