agentleFS
Sign inStart free
platformplatformplatformplatform/PlatformPlatform/.claude/skills/team-interrupt/SKILL.md

team-interrupt

Skill439 starsChanged 6 months agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run (use developer-cli exactly as written - do not expand to an absolute worktree path):

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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):
    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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free