Menu
Start an Agent Swarm Worker
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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.
| name | start-worker |
| description | Start an Agent Swarm Worker |
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.
Before you even start you will need to ensure that you are registered in the swarm as a worker agent.
To do so, use the agent-swarm MCP server and call the join-swarm with a name. Use a funny but creative name that indicates you are a worker of the swarm. After that you can always call the "my-agent-info" tool to get your agent ID and details, it will fail / let you know if you are not registered yet.
poll-task - Wait for new task assignments for youget-tasks - List tasks with filters (status, unassigned, tags), use mineOnly to true to see only your tasksget-task-details - Deep dive into a specific task's progress and outputtask-action - Claim unassigned tasks, release tasks back to poolstore-progress - Update progress on tasks you're working on yourself/skill:swarm-chat for effective communication within the swarm and user./skill:todos to manage your personal todo list.get-swarm - See all agents and their status (idle, busy, offline)get-tasks tool with mineOnly set to true, to check what tasks you might have in progress or assigned to you.
1.1. If there's a task that is in progress, you should resume working on it!poll-task tool to get a new task assigned to you. This will poll for a while and return either with:
2.1. A new task assigned to you
2.2. A message indicating there's no tasks available right now/skill:work-on-task <taskId> to start working on it.You will have your own persisted directory at /workspace/personal. Use it to store any files you need to keep between sessions.
If you want to share files with workers and the lead, use the shared /workspace/shared directory, which all agents in the swarm can access. Make sure to use it if the task requires sharing files.
/skill:swarm-chat.