Dispatching Parallel Agents
v0.1.0Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
⭐ 0· 96·0 current·0 all-time
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 (dispatch parallel agents for independent tasks) matches the SKILL.md instructions (how to identify independent domains, craft focused prompts, dispatch agents, review results). There are no unrelated environment variables, binaries, or installs requested. One implicit dependency is that the agent using this pattern will need access to the codebase/tests and a test runner to follow the examples — that assumption is reasonable for the stated purpose but is not explicitly declared.
Instruction Scope
Instructions remain within the stated purpose: create self-contained prompts, run separate agents, and review their outputs. The examples explicitly ask agents to read test files, run/modify tests, and make fixes — which is appropriate for debugging workflows but implies filesystem and repository access and the ability to edit code. This is expected but worth noting: the skill does not provide guardrails around concurrent edits or repository permissions, so callers must ensure agents have only the intended access and that changes are reviewed.
Install Mechanism
Instruction-only skill with no install spec, no code files, and no downloads — minimal surface area and no install-time risk.
Credentials
The skill requests no environment variables or credentials. That is proportionate for an instruction template. The SKILL.md does assume the operational environment will allow reading and editing tests and running the test suite; if those capabilities require credentials or tools in your environment, grant them deliberately.
Persistence & Privilege
always:false and default autonomous invocation are set (normal). The skill does not request persistent presence or claim to modify other skills or system-wide settings. However, because it encourages dispatching agents that may make commits/edits, consider reviewing change approvals and CI policies before allowing autonomous write actions.
Assessment
This is a coherent, low-risk instruction template for running independent agents in parallel. Before using it, ensure you intentionally grant the agent(s) access to the repository/test runner (read/write) only if you want them to modify code. Add guardrails: require human approval for commits or merges, run CI/full test suite after agent changes, and use locks or a coordinator to avoid conflicting concurrent edits. If you don't want agents to make changes autonomously, disable autonomous model actions or require explicit confirmation for any write operations.Like a lobster shell, security has layers — review code before you run it.
latestvk97bcep85dpy0h5jrqj8vrndnn83c1ht
License
MIT-0
Free to use, modify, and redistribute. No attribution required.