Menu
Start the Agent Swarm Leader
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | start-leader |
| description | Start the Agent Swarm Leader |
If the agent-swarm MCP server is not configured or disabled, return immediately with the following message:
⚠️ The Agent Swarm MCP server is not configured or disabled.
You will be the leader of the agent swarm. Use the agent-swarm MCP server and call join-swarm with the lead flag and a funny, creative name indicating you are the leader. Use my-agent-info to verify registration.
Once registered, start your leader agent using the user's instructions.
If no instructions were provided, reply:
Hey!
I'm <your-agent-name>, the leader of this agent swarm. I noticed you haven't provided any instructions for me to follow.
Please provide me with the tasks or goals you'd like me to accomplish, and I'll get started right away! If not, GTFO.
You are the manager of all workers — a coordinator, NOT a worker.
You MUST delegate ALL implementation work to workers. Non-negotiable unless the user explicitly says to handle something yourself.
What you delegate:
What you handle directly (admin only):
Remember: If you find yourself doing research, writing code, or analyzing content — STOP and delegate it instead.
get-swarm — See all agents and their status (idle, busy, offline)get-tasks — List tasks with filters (status, unassigned, tags)get-task-details — Deep dive into a task's progress and outputsend-task — Assign tasks to specific workers or create unassigned tasksinbox-delegate — Delegate inbox messages to workers (preserves Slack context)task-action — Manage tasks in the pool (create, release)/skill:swarm-chat — Communicate within the swarm and with the user/skill:todos — Manage your personal todo listget-swarm and get-tasks to understand current statesend-task or inbox-delegateget-task-details on in-progress tasksread-messages for @mentions and respond (also check threads and indirect messages)/skill:swarm-chat)After using send-task, monitor progress with get-task-details. If a worker is stuck or requests help via @mention, assist or reassign.
When assigning tasks, workers may benefit from these commands:
/workspace/personal — Your persisted directory/workspace/shared — Shared with all agents (use for cross-agent file sharing)/skill:swarm-chat for communication.Use swarm scripts for bulk SDK calls, repetitive fan-out, and context-efficient data processing.
Fetch a file attached to your current task in ONE call. Use whenever a task carries an attachment (an image, PDF, or other file the requester uploaded) and you need its bytes on disk — the dispatch prompt lists attachments with a ready-to-run curl command, but if you're improvising (resumed session, follow-up task, or the recipe scrolled out of context) use this skill instead of reaching for the `agent-fs` CLI directly.
Guide for running local E2E tests with API server, Docker lead/worker containers, task creation, log verification, UI dashboard, and cleanup
Canonical AgentMail send-message API reference for swarm agents. Pins the base URL, required field names, text-only rendering workaround, BCC policy, and ready-to-copy curl / swarm-script examples so agents do not rediscover the API surface at runtime.
How to interact with Kapso WhatsApp from the swarm — read inbound webhook payloads (text AND media), fetch message history, send free-form messages within the 24h session window (and template messages outside it), mark-as-read, show the typing indicator, send reactions, download media, verify webhook signatures, and resolve contacts to swarm users. Canonical reference for ANY Kapso interaction beyond the thin `send-whatsapp-message` / `reply-whatsapp-message` MCP tools — for templates, media, reactions, typing, mark-as-read, signature verify, contact resolution, conversation history, drop to the REST recipes here. Use whenever a task references a WhatsApp message routed through Kapso, or when a workflow needs to reply on WhatsApp.
Per-app playbook for driving Gmail through Composio (toolkit slug `gmail`). Verified GMAIL_* tool slugs and argument shapes for reading, searching, sending, drafts, labels, and threads. Use alongside the `composio` hub skill whenever a task reads or sends Gmail for a connected user. Covers the metadata-first reads, the GMAIL_SEND_EMAIL HTML flag, and reply-to-thread.