swarm-expert_skill

Overview

This skill is a multi-agent coordination expert for the agent-swarm MCP server. It helps you join and manage swarms, delegate and claim tasks, monitor swarm status, and handle agent-to-agent messaging. Use it to design and operate reliable multi-agent workflows and communication patterns.

How this skill works

The skill maps common coordination intents to MCP server tools such as join-swarm, get-swarm, get-tasks, send-task, task-action, store-progress, post-message, and read-messages. It inspects swarm membership, task lists and states, task dependencies, channel lists, and unread/mentioned messages, then issues the appropriate MCP calls to perform joins, delegation, claims, progress updates, or messaging. Responses include concise actions to follow and checks to verify success.

When to use it

• When you need to join a swarm as leader or worker and establish presence.
• When delegating work to specific agents or a shared pool of workers.
• When checking overall swarm health, agent status, or current assignments.
• When claiming, updating, or reporting progress on tasks.
• When sending or reading inter-agent messages, replies, or mentions.

Best practices

• Join the swarm with a clear name and isLead flag to establish role and visibility.
• Tag tasks and set dependsOnTaskIds to express dependencies and avoid blockers.
• Prefer assigning to a pool for flexible load balancing; assign to specific agents for specialized work.
• Poll get-tasks and get-task-details regularly to detect blocked or failed tasks early.
• Use post-message with channelId and @mentions for targeted agent coordination and threading.

Example use cases

• Start a leader session: join-swarm (isLead=true), list workers with get-swarm, send-task to assign subtasks, monitor progress with get-tasks.
• Worker workflow: join-swarm (isLead=false), poll-task for new assignments, claim via task-action, report via store-progress.
• Task delegation: create a detailed send-task with title, description, tags, and dependsOnTaskIds to coordinate multi-step work.
• Troubleshoot state: run get-tasks filtered by status or tags, then use get-task-details to inspect logs and outputs.
• Agent chat: list-channels, post-message with mentions for alerts, and read-messages (unreadOnly/mentionsOnly) to process responses.