Broadcast prompt

Skill LupusDei/adjutant/skills/broadcast-prompt

Broadcast a message into every active agent's Claude Code tmux session as a submitted prompt. Also sends persistent MCP messages as backup. Use when you need to inject a standing order, instruction, or announcement into all running agents at once.From its SKILL.md

Install

npx -y skills add LupusDei/adjutant --skill broadcast-prompt

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.2 KB, as published. Nobody here has run it

Broadcast Prompt

Deliver a message directly into every active agent's Claude Code prompt — submitted as a real prompt (with Enter) — and send a persistent MCP message copy.

Instructions

When the user invokes /broadcast-prompt <message>, follow these steps exactly:

Step 1: Extract the message

The <message> is everything after /broadcast-prompt . Preserve it exactly — whitespace, punctuation, newlines, all of it.

Step 2: Discover agents

Call the MCP tool:

list_agents({ status: "all" })

Record the full agent roster with their names and statuses.

Step 3: Discover live tmux sessions

Run:

tmux list-sessions -F "#{session_name}" 2>/dev/null || true

This gives you every active tmux session name. Agent sessions use the naming convention adj-swarm-{agentname}.

Step 4: Match agents to sessions

For each agent from Step 2:

Check if a tmux session named adj-swarm-{agentname} exists in the Step 3 output
Skip yourself (the executing agent) — do NOT send to your own session
Build three lists:
- tmux_targets: agents with a matching live tmux session (will get prompt + MCP message)
- mcp_only: agents without a tmux session (will get MCP message only)
- skipped: yourself

Step 5: Deliver to each tmux target

For each agent in tmux_targets, run these two commands sequentially:

tmux send-keys -t "adj-swarm-{name}" -l "{message}"
tmux send-keys -t "adj-swarm-{name}" Enter

Critical details:

The -l flag is mandatory — it sends the text literally, preventing tmux from interpreting spaces or special characters as key names
Enter is sent as a separate send-keys command, not embedded in the text
If send-keys fails for a specific agent, move that agent from tmux_targets to mcp_only and note the error

Step 6: Send persistent MCP messages

For every agent in both tmux_targets and mcp_only (everyone except yourself), send:

send_message({ to: "{agentname}", body: "{message}" })

This ensures agents that reconnect later still see the message in their inbox.

Step 7: Build and send the delivery report

Send a summary to the user:

send_message({ to: "user", body: "<delivery report>" })

The delivery report should contain:

## Broadcast Delivery Report

**Message:** {first 100 chars of message}...

**Delivered via tmux prompt ({count}):**
- agent-a
- agent-b

**MCP message only — no tmux session ({count}):**
- agent-c

**Skipped (self):**
- {your-name}

Also print the delivery report to stdout so the invoking user sees it immediately.

Notes

This skill requires tmux to be installed and running
If no tmux server is running, all agents will fall back to MCP-only delivery
The tmux session naming convention adj-swarm-{name} matches the Adjutant swarm spawner pattern
Messages sent via tmux are immediately submitted as prompts — agents will process them on their next turn