This skill allows you to communicate with and control other agents in the swarm using a file-based messaging system.
You communicate by writing JSON files to the requests directory and reading response files.
To send a message to a sub-agent, create a JSON file in the following location: ../../comms/requests/req_<unique_id>.json
JSON Schema:
{
"request_id": "req_123",
"type": "prompt",
"target_agent": "agent_1",
"prompt": "Your instructions to the agent here.",
"response_file": "../../comms/responses/res_123.json"
}
request_id: A unique identifier for the request.type: Must be "prompt" for sending instructions.target_agent: The name of the target window (e.g., "agent_1", "agent_2").prompt: The text message or command you want the agent to execute.response_file: The relative path where the Orchestrator will write the response.The background Orchestrator will pick up your request, send it to the agent, and write the response to the specified response_file. You should poll for the existence of the response file and read its content.
Response Schema:
{
"request_id": "req_123",
"status": "success",
"output": "The raw terminal output from the agent."
}
You can also send control commands to create or kill agents.
Create Agent Example:
{
"request_id": "req_create",
"type": "control",
"action": "create",
"target_agent": "agent_new",
"conversation_id": "optional_existing_conv_id",
"response_file": "../../comms/responses/res_create.json"
}
Kill Agent Example:
{
"request_id": "req_kill",
"type": "control",
"action": "kill",
"target_agent": "agent_1",
"response_file": "../../comms/responses/res_kill.json"
}
You can see active agents by listing the windows in the tmux session, or assume agent_1, agent_2, etc., are available based on the setup.
request_ids.