Team Interrupt
SkillCommunicationSend 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.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Team Interrupt skill
What this skill tells your AI
The instructions your AI receives, as published by platformplatform/platformplatform in .claude/skills/team-interrupt/SKILL.md and read by ahel’s review.
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
- Run (use
developer-cliexactly as written - do not expand to an absolute worktree path):dotnet run --project developer-cli -- claude-command send-interrupt-signal --team <team> --agent <agent> - Capture the stdout line - a single
#<id>interrupt ID. - Send a follow-up
SendMessageto the same agent with the body prefixed by that ID:#<id> <your instruction> - 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.
Signals
- GitHub stars
- 441
- Forks
- 52
- Last commit
- Jul 2026
Advanced
- Catalog kind
- skill
- Gateway key
team-interrupt- Source
- github.com/platformplatform/platformplatform