Send an interrupt signal to a working team agent. Use when an agent is actively running and you need to send it a message without having to wait until it has processed all other messages.
Installs into .claude/skills of the current project.
Are you the author of Team Interrupt?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/platformplatform-team-interrupt)
---
name: team-interrupt
description: Send an interrupt signal to a working team agent. Use when an agent is actively running and you need to send it a message without having to wait until it has processed all other messages.
---
# Team Interrupt
`SendMessage` is for idle/hibernated agents only. If the agent is working, the message sits in the queue and is processed later against stale context - answers will be obsolete and queued instructions may already be wrong. To reach a working agent, use Interrupt + `SendMessage`. Never queue status checks, redirects, or corrections behind active work.
## Procedure
1. Run (use `developer-cli` exactly as written - do not expand to an absolute worktree path):
```bash
dotnet run --project developer-cli -- claude-command send-interrupt-signal --team <team> --agent <agent>
```
2. Capture the stdout line - a single `#<id>` interrupt ID.
3. Send a follow-up `SendMessage` to the same agent with the body prefixed by that ID:
```
#<id> <your instruction>
```
4. STOP - no follow-ups.
The ID links the signal to the correct queued message; the active agent skips stale messages until it sees the matching ID.
