From swarp
Agent orchestration — setup, create agents, deploy, manage. Use when user says /swarp, asks about agents, wants to deploy or manage remote Claude agents.
How this skill is triggered — by the user, by Claude, or both
Slash command
/swarp:swarpThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
SWARP deploys remote Claude agents on Fly Sprites, orchestrated through a central gRPC router.
SWARP deploys remote Claude agents on Fly Sprites, orchestrated through a central gRPC router.
If the user runs /swarp or asks about setting up agents, call the swarp_onboard tool with no arguments. It will tell you the current setup status and what to do next. Follow its instructions exactly.
The onboard tool manages a 4-phase workflow:
Each phase must complete before the next can start. The tool enforces this — do not try to skip phases.
Run commands directly. Do not ask the user to run things for you. Claude Code's permission system is the gate — if a command needs approval, the user will be prompted automatically. For example:
fly auth login yourself (Claude Code will handle the interactive prompt if needed, or the user will be prompted to approve).flyctl status or sprite list yourself.flyctl orgs list or gh secret list? Just run them.Only stop to ask the user when you need information from them (e.g., "what should the agent do?"), not when you need to execute something.
When asking the user to make a decision (which org, which model, which mode), always use AskUserQuestion with structured options instead of asking in free text. Discover the options yourself first (e.g., run flyctl orgs list to find orgs), then present them as choices. This gives the user a clean click-to-select UI instead of making them type something they don't know off the top of their head.
/swarp (no arguments)Call swarp_onboard with action status. Show the result to the user.
/swarp create <name>Help the user create an agent. Ask:
Generate agents/<name>/agent.yaml with appropriate modes based on the answers. Use the Write tool to create the file.
/swarp deploy <name>Call the swarp_deploy MCP tool with the agent name. This triggers a cost confirmation prompt — the user must approve before infrastructure is created.
/swarp deploy --allDeploy all agents found in the agents directory. Call swarp_deploy for each one. Each triggers its own cost confirmation.
/swarp destroy <name>Call the swarp_destroy MCP tool with the agent name. This triggers a confirmation prompt warning about data loss.
/swarp statusCall swarp_status MCP tool (no arguments for all agents, or with agent name for one).
When creating agents, generate YAML like this:
name: <agent-name>
version: '1.0.0'
grpc_port: 50052
router_url: '${SWARP_ROUTER_URL}'
preamble: |
<describe what the agent does and its personality>
modes:
- name: <primary-mode>
description: '<what this mode does>'
model: <claude-sonnet-4-6 or claude-haiku-4-5-20251001>
max_turns: <10-40 depending on complexity>
timeout_minutes: <5-30>
prompt: '{{ task }}'
allowed_tools:
- Read
- Edit
- Write
- Bash
- Glob
- Grep
swarp_deploy, swarp_deploy_router, and swarp_destroy all trigger cost confirmation hooks. The user WILL be prompted by Claude Code before these execute. Set their expectations: "This will create infrastructure — you'll see a cost estimate and need to approve."npx claudepluginhub dl3consulting/swarp --plugin swarpProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.