Parallel Agents
v1.0.1Use when facing 2 or more independent tasks that can be worked on without shared state - dispatches parallel subagents using sessions_spawn for concurrent in...
⭐ 0· 131·0 current·0 all-time
by@axelhu
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 subagents for independent tasks) matches the SKILL.md content. The instructions only require the agent to create sessions with sessions_spawn, read test files, run tests, and propose or apply fixes — all coherent with the stated purpose.
Instruction Scope
The instructions explicitly direct subagents to read project files, run tests, and make code fixes (with constraints such as 'don't change other code'). This is expected for a code-fixing parallel-agents skill, but it does mean the skill involves filesystem access and code modification. The guidance is high-level and relies on the orchestrating agent to enforce constraints and resolve merge/conflict risks, so users should ensure human review/controls are in place before accepting changes.
Install Mechanism
Instruction-only skill with no install spec and no code files. Nothing is downloaded or written to disk by an installer, which is the lowest-risk install surface.
Credentials
No required environment variables, credentials, or config paths are declared, and the SKILL.md does not request secrets or external tokens. The described operations (sessions_spawn, local cwd) do not require additional credentials beyond whatever the agent already has to access the project workspace.
Persistence & Privilege
always is false and there is no attempt to modify other skills or system-wide settings. Autonomous invocation remains allowed (platform default) but the skill itself does not demand elevated or persistent privileges.
Assessment
This skill appears coherent and limited to orchestrating parallel subagents, but it will enable agents to read and modify your codebase — so take precautions: run it on a cloned repo or feature branch, require a human review step before merging any automated changes, ensure CI runs the full test suite after integration, and watch for conflicting edits from concurrent agents. Do not run it against repositories containing sensitive secrets or production-only resources without additional access controls. If you need stronger guarantees, ask for more explicit safe-guards in the prompts (e.g., automatic branch creation, per-agent file locks, and an explicit 'propose' vs 'apply' mode).Like a lobster shell, security has layers — review code before you run it.
latestvk97cpzkptappsbcydr5tymmtgd83nzky
License
MIT-0
Free to use, modify, and redistribute. No attribution required.