Batch

v1.0.0

Process multiple items with progress tracking, checkpointing, and failure recovery.

2· 1.2k·7 current·7 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the included SKILL.md, errors.md, and strategies.md: all focus on batch processing, progress reporting, checkpointing, retries, and rollback. There are no unrelated environment variables, binaries, or install steps requested.
Instruction Scope
Runtime instructions stay within batch-processing concerns (dry runs, progress messages, checkpointing, retry policies, saving failed items to local files). The files reference local paths (/tmp/*), retry/backoff logic, and delegation to sub-agents in a generic way; they do not instruct reading unrelated system credentials or contacting external endpoints.
Install Mechanism
No install spec and no code files to execute; this is an instruction-only skill, which means nothing new is written to disk or downloaded during install.
Credentials
The skill declares no required environment variables, credentials, or config paths. The instructions reference only local artifacts (checkpoints, backups, /tmp files), which is proportionate to the described tasks.
Persistence & Privilege
always is false and there are no claims to modify other skills or system-wide agent settings. The skill does instruct writing checkpoints and failure logs to local paths (normal for batch tools) but does not request persistent elevated privileges.
Assessment
This skill is coherent and focused on batch processing, but before using it: run the recommended dry run on a small sample; review any destructive steps carefully (it explicitly prompts for confirmation for deletes); ensure backups exist for any data the batch will modify; verify that saving checkpoints/failures to /tmp is acceptable in your environment; and if you enable delegation to sub-agents, confirm you trust the agent's autonomy and the mechanism it will use (the docs mention delegation but don't specify transport or endpoints).

Like a lobster shell, security has layers — review code before you run it.

latestvk97fywd97xpyq5ysqnvv3jq45h80y9p2

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments