Install any skill in seconds. Free to start, no credit card required.
Get Started Free →platformplatform/team-interrupt
Send an interrupt signal to a working team agent.
2 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 2 comparable cases; this report requires 8.
A test case the skill fixed. Same model, same prompt, with and without the skill.
You ran the signal command for team Frontend agent UI-1 and received stdout line '4092'. Write the message payload to send to UI-1 instructing them to switch to the dark theme branch.
| Checked | Without skill | With skill |
|---|---|---|
| Prefixes the message body with #4092 | Missed | Passed |
The instructions your model reads when the skill loads.
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.
developer-cli exactly as written - do not expand to an absolute worktree path):
dotnet run --project developer-cli -- claude-command send-interrupt-signal --team <team> --agent <agent>
#<id> interrupt ID.SendMessage to the same agent with the body prefixed by that ID:
#<id> <your instruction>
The ID links the signal to the correct queued message; the active agent skips stale messages until it sees the matching ID.
test cases passed with the skill
More skills from the same source and nearby in the registry, with their headline benchmark lift.