multi agent analysis and execution
v1.0.4Orchestrate complex multi-agent workflows with explicit coordinator planning, execution governance, and *automatic output management*. Each skill run creates...
⭐ 0· 45·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
Name/description (multi-agent orchestration) aligns with the SKILL.md and README: both describe planning, spawning agents, sequencing, output management, reporting, and cleanup. The required artifacts and filesystem writes are consistent with an orchestration/coordinator skill.
Instruction Scope
Instructions are focused on orchestration and file-scoped outputs (per-run directories, prompts, outputs, reports). This is within scope, but the skill mandates producing and persisting prompts and outputs (especially in debug mode) and forbids giving direct answers. Persisting prompts may capture user-provided sensitive data if the user includes secrets in the problem statement; the skill does not prescribe sanitization of user inputs.
Install Mechanism
No install spec and no code files — instruction-only. This is the lowest-risk install model and matches the stated behavior.
Credentials
The skill declares no required environment variables or credentials, which matches the registry metadata. The SKILL.md does mention that sub-agents that require credentials should obtain them via ENV or other tools; this is advisory only and not a declared requirement. Users should be cautious about providing secrets in prompts or files created by the coordinator.
Persistence & Privilege
The skill does not request always:true, does not install or modify other skills, and only instructs the coordinator to create per-run directories under a workspace (relative paths only). It requires filesystem writes but does not request elevated or cross-skill privileges.
Assessment
This skill is a coherent orchestration template that will create per-run directories, generate planning artifacts and agent prompts, spawn and wait for sub-agents, and persist outputs (especially in debug mode). It does not require credentials or install anything, but it will write files that can contain the problem text and generated prompts — avoid including secrets (API keys, tokens, passwords) in your problem statement or prompts. If you plan to run in Debug mode, expect persistent artifacts (prompts, outputs) on disk; decide whether that data retention is acceptable. Confirm you want the coordinator to refuse direct answers (the skill enforces 'no direct answers') and to always follow the full 5-phase contract before invoking. If you need the coordinator to access credentials for sub-agents, prefer providing them through platform-approved secret mechanisms rather than embedding them in prompts or files.Like a lobster shell, security has layers — review code before you run it.
latestvk97cq51yb3c6zfw1nges5tdtch842nsq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.