llm-work-via-subagents
Skill1 starsChanged 3 months agoLicence not identifiedView on GitHub
When you (an agent that can spawn subagents) are about to write a script that calls an LLM API with a key to do BULK or REPEATED LLM work — labeling, classifying, extracting, reviewing, summarizing, or judging across many items, or running an evaluator ensemble — stop and spawn parallel subagents instead. Spawning is more efficient, needs no API key, and carries no rate-limit/retry/cost plumbing. Trigger on ANY batch or iterative LLM task, even with no ML, annotation, or training involved: "label this corpus", "classify these records", "review these documents", "extract fields from these files", "summarize each of these", "have a few models check this", "process these messages/emails/transcripts". The smell to catch is "I'll write a Python loop that calls the API for each item" — that is the signal to use subagents. Does NOT apply to a single one-off LLM call, or to genuinely unattended very-large batch jobs (see the exception below).
In this repository36 other files it gives its agents.
- ai-epistemic-discoverySkill
- anonimizacao-documentosSkill
- blank-sheet-redesignSkill
- brazilian-web-designSkill
- cobogo-consumer-synergySkill
- cobogo-design-reviewSkill
- consulta-dare-sefinSkill
- convert-to-pdfaSkill
- datajudSkill
- franklin-blogSkill
- free-gpuSkill
- juris-tjroSkill
- jus-brSkill
- legal-argument-leanSkill
- license-enforcementSkill
- liteboxSkill
- loop-engineeringSkill
- mbqlSkill
- meme-imageSkill
- notebooklm-processosSkill
- okf-agent-skillsSkill
- opf-finetuneSkill
- paddleocrSkill
- pdf-compressionSkill
- pdf-to-markdownSkill
- revisao-minutasSkill
- ruff-strict-complianceSkill
- software-reviewSkill
- solo-builder-triageSkill
- suno-curatorSkill
- suno-profileSkill
- text-meme-injectionSkill
- toe-arena-tieringSkill
- verne-orchestrationSkill
- vibevoice-asrSkill
- youtube-playlist-mp3Skill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

