agent-swarm-deployer

Solid

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.

AI & Automation 229 stars 38 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
79
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

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

Details

Author
OneWave-AI
Repository
OneWave-AI/claude-skills
Created
9 months ago
Last Updated
1 weeks ago
Language
N/A
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

agent-swarm

(Industry standard: Parallel Agent) Primary Use Case: Work that can be partitioned into independent sub-tasks running concurrently across multiple agents. Parallel multi-agent execution pattern. Use when: work can be partitioned into independent tasks that N agents can execute simultaneously across worktrees. Includes routing (sequential vs parallel), merge verification, and correction loops.

4 Updated 2 days ago
richfrem
AI & Automation Solid

agent-army

Deploy a 2-layer parallel agent hierarchy for large, parallelizable work — big refactors, multi-file migrations, codebase-wide audits, bulk generation. A top-tier commander (Fable or Opus) orchestrates the swarms; the user picks a power level (Max Power / Heavy / Balanced / Economy) that sets the Opus/Sonnet/Haiku model mix per layer. Layer 1 is 3-50+ specialist agents, each with its own full context window; Layer 2 is 2+ sub-agents per member. Includes git safety, tiered sizing, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.

229 Updated 1 weeks ago
OneWave-AI
AI & Automation Listed

swarm

Parallel sub-agent fan-out. When a turn has 2+ INDEPENDENT read-only sub-questions (multi-source research, multi-target verification, several independent file reads, multiple log/config/db inspections), spawn one sub-agent per question in a SINGLE message so they run concurrently — instead of doing serial reads. Invoke whenever you catch yourself about to do a 3rd serial Bash/Read/Grep in one turn on independent questions.

1 Updated 3 days ago
LogicLabsAI