Agent Swarm Deployer logo

Agent Swarm Deployer

Organization
OneWave-AI
agent-swarm-deployer

Deploys swarms of sub-agents for massive parallel data processing tasks. Unlike agent-army (which is for code changes), this is for DATA tasks -- processing 1000 documents, analyzing datasets, bulk content generation. Configurable swarm size, task distribution, result aggregation, progress tracking, and error recovery.

Overview

PublisherOneWave-AI
Repositoryclaude-skills
Skill nameagent-swarm-deployer
Stars
293
Forks
49
Bundled files
6
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 6 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by OneWave-AI on GitHub. Read the source before you install it.

Installation

Install the Agent Swarm Deployer AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git /tmp/claude-skills
mkdir -p .claude/skills
cp -r /tmp/claude-skills/agent-swarm-deployer .claude/skills/agent-swarm-deployer
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Agent Swarm Deployer in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Agent Swarm Deployer on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Agent Swarm Deployer is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Agent Swarm Deployer

Deploy a swarm of parallel sub-agents to process massive, independent data tasks (documents, records, rows, items) and aggregate the results. Use this for data operations; use agent-army for code changes.

Contents

  • references/overview.md -- swarm vs army comparison, use cases, architecture diagram
  • references/swarm-design.md -- input/output schemas, batch-size and swarm-size formulas, scaling guidelines
  • references/agent-brief.md -- agent brief template, data distribution methods, progress tracking
  • references/aggregation-recovery.md -- merge logic, completeness validation, retry strategy, error-handling table
  • references/output-formats.md -- CSV/JSON/Markdown/individual-file outputs, final summary report
  • references/task-configs.md -- ready-made configs for sentiment, lead scoring, content generation, summarization

Workflow

  1. Understand the task. Pin down five things before deploying anything: data source, operation per item, output format, output destination, and quality/validation requirements. If any is ambiguous, ask the user first -- a wrong spec wastes all agent compute.

  2. Intake and inventory. Glob/Bash to locate and count items. Read 3-5 samples to learn structure. Estimate tokens per item and total. Report an intake summary (source, total count, item format, sample structure, token estimate).

  3. Detect input schema and define output schema. Derive the input schema from samples; define the exact output schema the task requires. See references/swarm-design.md.

  4. Design the swarm. Compute batch size from token budget (70% of ~200K usable context per agent) and swarm size from total items. Cap at 20 agents per wave; split into waves beyond that. Present the swarm plan and agent assignments, then get approval. See references/swarm-design.md.

  5. Prepare agent briefs. Build a self-contained brief per agent: role, task, input data, output schema with example, quality rules, error protocol, and strict JSON output format. See references/agent-brief.md.

  6. Distribute data and deploy. Choose a distribution method for the source type (pre-split CSVs/JSON with Bash; embed inline for small sets; pass file paths for directories). Launch up to 20 agents in parallel via the Agent tool with run_in_background: true, sending all calls in one message. Run later waves after the prior wave completes. See references/agent-brief.md.

  7. Track progress. As agents return, record status, processed counts, and cumulative coverage. See references/agent-brief.md.

  8. Collect and aggregate. Parse each agent's JSON; validate schema, completeness, and duplicates. Merge into one ordered output and extract failures. Report an aggregation summary with a coverage check and failure analysis. See references/aggregation-recovery.md.

  9. Recover failures. Queue all failed and skipped items, deploy a retry agent with enhanced instructions, cap at 2 retries, and mark survivors "unrecoverable". Flag the user if unrecoverable items exceed 10%. See references/aggregation-recovery.md.

  10. Write output and summarize. Produce the requested format (CSV, JSON, Markdown, or individual files) plus a final summary covering execution, results, quality metrics, patterns observed, and cost. See references/output-formats.md.

Anti-Patterns to Avoid

  1. Do not use a swarm for sequential tasks. If item N depends on item N-1, use a chain instead.
  2. Do not deploy one agent per item. Batch items; one-per-agent wastes overhead.
  3. Do not skip schema definition. Without a schema, merging results from many agents becomes unreliable.
  4. Do not ignore failures. At 99% success, 1% of 10,000 items is still 100 failures. Always run retries.
  5. Do not deploy without a sample run. Process 5 items manually first to validate the task and output quality before scaling.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Agent Swarm Deployer AI skill do?

Deploys swarms of sub-agents for massive parallel data processing tasks. Unlike agent-army (which is for code changes), this is for DATA tasks -- processing 1000 documents, analyzing datasets, bulk content generation. Configurable swarm size, task distribution, result aggregation, progress tracking, and error recovery.

Why use Agent Swarm Deployer on TypingMind?

Because you install it once and use it with any model. Agent Swarm Deployer is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Agent Swarm Deployer in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/OneWave-AI/claude-skills/tree/main/agent-swarm-deployer. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Agent Swarm Deployer?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Agent Swarm Deployer?

As many as you like. As long as a model supports skills, you can use Agent Swarm Deployer with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Agent Swarm Deployer AI skill free?

Yes. It is published on GitHub by OneWave-AI under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇