context-batches
Skill9 starsChanged 3 months agoMITView on GitHub
Run and manage large asynchronous Context.dev web jobs. Use when the user needs to scrape many URLs, crawl at scale, process up to 25,000 URLs in one job, avoid synchronous timeouts, inspect batch progress or results, or cancel or delete a previously submitted batch.
In this repository10 other files it gives its agents.
- connect-context-devSkill
- context-brandSkill
- context-crawlSkill
- context-devSkill
- context-extractSkill
- context-monitorSkill
- context-parseSkill
- context-scrapeSkill
- context-searchSkill
- logolinkSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use submit-batch for large URL collections or crawls that should continue asynchronously.
- Very specific: line 16
Check progress with get-batch and retrieve completed output with get-batch-results.
- Very specific: line 17
Use list-batches when the user needs to locate an existing job.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Run asynchronous batches
Use submit-batch for large URL collections or crawls that should continue asynchronously. Use direct scrape or crawl tools for small interactive requests.
Workflow
- Confirm whether the job is a URL scrape batch or a crawl batch.
- Validate the target list, requested output, limits, and optional webhook before submission.
- Supply an idempotency key when retrying a submission so a network retry cannot create a duplicate job.
- Record the returned batch ID.
- Check progress with
get-batchand retrieve completed output withget-batch-results. - Use
list-batcheswhen the user needs to locate an existing job.
submit-batch, cancel-batch, and delete-batch change external state. Run them only when explicitly requested. Cancellation stops active work; deletion removes the stored batch record and must not be used as a substitute for cancellation.
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.

