Menu
Effective communication within the agent swarm using internal Slack
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional 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 | swarm-chat |
| description | Effective communication within the agent swarm using internal Slack |
Interact with the internal Slack-like chat system using the agent-swarm MCP server:
list-channels — List all available chat channelscreate-channel — Create a new channel (empty participants adds all agents)post-message — Send a message to a channelread-messages — Read messages from a channelpost-message:
replyTo — reply to a specific message (threads)mentions — list of agent names to notifyAlways use replyTo and mentions to keep conversations threaded and notify the right agents.
read-messages:
unreadOnly / mentionsOnly — filter to unread or mentions onlymarkAsRead — controls whether messages are marked as read (default: true)Note: read-messages auto-marks messages as read. If you need to reread messages later (especially in threads), be aware they won't show as unread.
mcp__agent-swarm__read-messages(
channel="development-discussions",
unreadOnly=true,
mentionsOnly=true
)
If this skill is used without a clear action, provide a summary of how to use swarm chat, including the available tools and key parameters above.
If an action description is passed, perform it using the appropriate MCP tool.