← Spaces: Coding AgentsCONTENT HISTORY
WHAT CHANGED
Update to Spaces: Coding Agents
Snapshot Nov 14, 2026 · 01:37 UTC · version 1.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Spaces: Coding Agents and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use when the user asks what their coding agents are doing, whether an agent is done, stuck, or waiting on them, or wants a status roll-up of agents across Spaces devices. Read-only - it summarizes who is working, blocked, done, or waiting on input. Do not use for CI builds, deploys, or other jobs that are not coding agents, or to answer a blocked agent (use unblock).",
"included_files": [],
"name": "standup",
"skill_md_contents": "---\nname: standup\ndescription: Use when the user asks what their coding agents are doing, whether an agent is done, stuck, or waiting on them, or wants a status roll-up of agents across Spaces devices. Read-only - it summarizes who is working, blocked, done, or waiting on input. Do not use for CI builds, deploys, or other jobs that are not coding agents, or to answer a blocked agent (use unblock).\n---\n\nGive the user a status roll-up of their agents. Read-only: never send input to a terminal from this skill.\n\nRequires the Spaces MCP server (`spaces` tools). If they are not available, use the setup skill instead.\n\n## Gather\n\n1. `spaces_device_list` to enumerate paired devices.\n2. `spaces_agent_list` for this machine and for each reachable paired device (pass `device`).\n3. For any agent whose status or note leaves its situation unclear - especially blocked ones - read `spaces_terminal_tail` (`lines`: 30-40) on its session to see what it is actually doing or asking. Skip the tail for agents whose list row already tells the story.\n\n## Report\n\nOrder by urgency: agents needing attention first (blocked, waiting on a dialog or question), then actively working, then done/exited.\n\nFor each agent give: label, project/workspace and branch, device (when not this machine), one line on what it is doing or stuck on (from its note or tail), and its `spaces://terminal` deep link. For blocked agents, quote the actual question or dialog from the tail so the user can decide without opening the terminal.\n\nClose with a one-line headline: how many working, blocked, and done. If nothing is running anywhere, say exactly that.\n"
}SHA-256 of public snapshot: c230114a0807ef0551f126d11085164f3489c981ec2ac71832aa39734e2791f6