agent-swarm-deployer

Deploys parallel sub-agent swarms to process large datasets and aggregate results.

1|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/th-efool/SKILLS --skill agent-swarm-deployer-th-efool
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-swarm-deployer
Source: https://github.com/th-efool/SKILLS/tree/main/agent-swarm-deployer
Command: npx skills add https://github.com/th-efool/SKILLS --skill agent-swarm-deployer-th-efool

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Processing hundreds or thousands of documents, records, or rows one at a time is slow and error-prone. This Skill splits massive independent data tasks into batches, deploys parallel sub-agents to process them, and aggregates validated results with failure recovery. ## Core Features & Use Cases - Swarm Design & Sizing: Computes batch size from token budgets and swarm size from total items, capping at 20 agents per wave with multi-wave deployment for larger jobs. - Structured Agent Briefs: Generates self-contained briefs per agent with input data, output schemas, quality rules, and error protocols so results merge reliably. - Aggregation & Recovery: Validates schema compliance, completeness, and duplicates, then retries failed items up to two times before marking them unrecoverable. - Use Case: Score 2,000 sales leads against ICP criteria by splitting them into batches of 40, deploying 50 agents across 3 waves, and merging the scored results into a single CSV with a failure report. ## Quick Start Use the agent-swarm-deployer skill to analyze the sentiment of all 1,000 customer reviews in reviews.csv and output the results as a single CSV.

Frequently Asked Questions about agent-swarm-deployer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I process thousands of documents in parallel with AI agents?▼

Split the items into batches sized by token budget, then deploy up to 20 sub-agents in parallel per wave, each with a self-contained brief and output schema. Results are merged, validated for completeness, and failed items are retried up to two times.

What is the difference between agent swarm and agent army?▼

Agent swarms handle data processing tasks like analyzing documents, scoring leads, or generating content at scale. Agent armies handle code changes across files where import graphs and build verification matter.

How is batch size calculated for parallel data processing agents?▼

Batch size equals 70% of a 200K token context budget divided by tokens per item, including input, output, and overhead. Practical limits are 5 to 200 items per agent, with 20-80 being the sweet spot for text tasks.

What happens when some items fail during swarm processing?▼

Failed and skipped items are collected into a retry queue and processed by a retry agent with enhanced instructions. After two retries, survivors are marked unrecoverable, and the user is flagged if unrecoverable items exceed 10%.

When should I not use a parallel agent swarm?▼

Avoid swarms for sequential tasks where item N depends on item N-1; use a chain instead. Also avoid one agent per item, skipping schema definition, or deploying without a 5-item sample run to validate output quality first.