llm-work-via-subagents

Replaces scripted LLM API loops with parallel subagent orchestration for batch tasks.

1|Updated May 8, 2026
One-click install
npx skills add https://github.com/franklinbaldo/skills --skill llm-work-via-subagents-franklinbaldo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: llm-work-via-subagents
Source: https://github.com/franklinbaldo/skills/tree/main/llm-work-via-subagents
Command: npx skills add https://github.com/franklinbaldo/skills --skill llm-work-via-subagents-franklinbaldo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents often reach for a Python script that loops over items calling an LLM API, reinventing authentication, rate-limit handling, retries, and cost plumbing. This Skill redirects that instinct toward spawning parallel subagents inside the current session, which is faster to set up and requires no API key. ## Core Features & Use Cases - Sharded batch processing: Split a corpus into batches and run one subagent per batch for labeling, classifying, extracting, or summarizing many items, then merge structured results. - Role-based ensembles: Spawn one subagent per role with differentiated briefs for evaluator ensembles, multi-rater review, red-team checks, or multi-rubric scoring. - Clear boundary guidance: Distinguishes when subagents win (interactive, hundreds-to-thousands of items, judgment-heavy work) from the one real exception (unattended very-large batch jobs like nightly CI re-tagging of tens of thousands of rows). - Use Case: You need to label 2,000 documents with categories. Instead of writing a for doc in docs: client.messages.create(...) loop, shard the documents across parallel labeling subagents and merge their JSON output. ## Quick Start Ask the agent to label, classify, or summarize your batch of documents by spawning parallel subagents instead of writing an API-calling script.

Frequently Asked Questions about llm-work-via-subagents

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

FAQPage Schema
How do I label a large corpus of documents with an LLM?▼

Shard the corpus into batches and spawn one labeling subagent per batch with the same brief, then merge their structured output. This avoids writing an API loop with authentication, rate-limit, and retry plumbing.

When should I use subagents instead of calling an LLM API in a script?▼

Use subagents for interactive work at human scale, roughly hundreds to low thousands of items, especially tasks needing judgment or ensembles. Reserve scripted API calls for unattended very-large batch jobs like nightly CI pipelines over tens of thousands of rows.

How do I run an evaluator ensemble with multiple LLM judges?▼

Spawn one subagent per role, each with its own differentiated brief, in parallel. Differentiated briefs decorrelate outputs and errors, which is the point of an ensemble, and the orchestrator merges the verdicts.

Do subagents need an API key for batch LLM work?▼

No. Subagents run inside the existing agent harness, so there is no API key, rate-limit handling, retry logic, or cost accounting to build. The orchestrator dispatches briefs and collects structured results.

When is a scripted LLM API call the right choice?▼

Scripted calls fit unattended, very-large batch work where spawning is impractical: tens of thousands of items, scheduled CI runs, or pipelines that must run reproducibly without an agent in the loop, often against a cheaper model.