Start Worker

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

.agents/skills/dashboard-ui

.agents/skills/swarm-local-e2e

.claude/skills/dashboard-ui

.claude/skills/swarm-local-e2e

AGENTS.md

Audit 0.4.1 · source sha 4df377778267 · 14 Oct 2026Report an issue or request a re-scan

• Publisherdesplega-ai GitHub organizationOwner of the repository this skill is read from
• Source folderdesplega-ai/agent-swarm/plugin/pi-skills/start-workerThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict4df377778267A new audit runs when the source changes
• Repository statusNot archivedPushed today
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Start an Agent Swarm Worker

---
name: start-worker
description: Start an Agent Swarm Worker
---

# Agent Swarm Worker

# Initial disclaimer

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.
```

## Agent Swarm Worker Setup

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.

## Tools Reference

### Your tasks

- `get-tasks` - List tasks with filters (status, unassigned, tags), use `mineOnly` to true to see only your tasks
- `get-task-details` - Deep dive into a specific task's progress and output

### Managing swarm tasks:

- `task-action` - Claim unassigned tasks, release tasks back to pool
- `store-progress` - Update progress on tasks you're working on yourself

### Management:

- Use `/skill:swarm-chat` for effective communication within the swarm and user.
- Use the `/skill:todos` to manage your personal todo list.
- `get-swarm` - See all agents and their status (idle, busy, offline)

## Workflow

1. Call `get-tasks` with `mineOnly` set to true to see the tasks assigned to you.
2. If one is `pending` or `in_progress`, call `/skill:work-on-task <taskId>` and work on it.
3. Otherwise stop. The swarm assigns tasks to you and opens each one with `/skill:work-on-task <taskId>`; you do not poll.

## Filesystem

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.

## Communication Etiquette

- ONLY follow-up if clearly stated by the user or the lead. Do NOT send random updates about your status unless explicitly requested.
- When communicating, ALWAYS use `/skill:swarm-chat`.

Excerpt, first 2,232 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/desplega-ai/agent-swarm
git -C agent-swarm checkout 4df377778267

Works in

1. 2026-10-14
   !CAUTION B 89 / 100

   first audit · source 4df377778267

Questions about Start Worker

• github.com/desplega-ai/agent-swarm/tree/main/plugin/pi-skills/st — the audited source at commit 4df377778267 and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology