multi task
v1.0.0Orchestrate parallel execution of batch tasks by splitting work into independent units and dispatching them to multiple subagents simultaneously. Use this sk...
⭐ 1· 319·0 current·0 all-time
byBright Ween@brightween
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (parallel batch orchestration) matches the SKILL.md content: it explains identifying work units, building per-task prompts, and dispatching parallel subagents via the Task/Skill tools. No unrelated credentials, binaries, or installs are requested.
Instruction Scope
The instructions explicitly direct the agent to read project files, create output directories (mkdir -p), use absolute filesystem paths, and include shared context verbatim inside each subagent prompt. That behavior is consistent with batch processing but can cause wide file read/write activity and repeated replication of any included context (potentially exposing sensitive data across many subagents). The skill also relies on platform Task and Skill tools to spawn subagents; those are expected for this capability but mean the agent will autonomously invoke other tools/skills during operation.
Install Mechanism
No install spec or code files — instruction-only. Nothing is downloaded or written to disk by installing the skill itself, minimizing install-time risk.
Credentials
The skill requests no environment variables, credentials, or config paths. All required inputs are user-supplied (file lists, templates). This is proportionate to its stated purpose.
Persistence & Privilege
always is false and the skill does not ask to modify other skills or system-wide settings. It can be invoked autonomously (platform default), which is expected for a dispatch/orchestration skill.
Assessment
This skill appears to do what it says — orchestrate parallel tasks — and it has no hidden installs or credential requests. Before using it, consider: (1) the skill's prompts instruct the agent to read and write files using absolute paths and to duplicate any shared context verbatim across many subagents — avoid including passwords, API keys, or other secrets in that shared context; (2) test first with a small pilot (the skill itself recommends pilots) to confirm behavior and resource usage; (3) if you don't want the agent to access certain directories, don't provide those paths and avoid granting file-system permissions; (4) be cautious about allowing the agent to invoke other installed skills automatically — ensure those skills are trusted, since the orchestration will call them on your behalf. If you want a tighter safety posture, require explicit confirmation before dispatching waves or restrict inputs to non-sensitive test data.Like a lobster shell, security has layers — review code before you run it.
latestvk9771bdcbymc5qmnp79mx1yptx820rz0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.