Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From swarmdo-swarm
Stream live swarm events using the Monitor tool for real-time observability
How this skill is triggered — by the user, by Claude, or both
Slash command
/swarmdo-swarm:monitor-streamThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use the Monitor tool to stream swarm events in real time instead of polling:
Use the Monitor tool to stream swarm events in real time instead of polling:
Run via Monitor: npx @swarmdo/cli@latest swarm watch --stream
This streams NDJSON events for agent spawns, task completions, memory writes, and health checks. Each stdout line triggers a notification.
For one-shot status, use MCP: mcp__swarmdo__swarm_status or mcp__swarmdo__swarm_health.
Prefer Monitor over polling swarm status in a loop. See ADR-091 for rationale.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
npx claudepluginhub swarmdo/swarmdo --plugin swarmdo-swarm