Agents Orchestrator
v1.0.0Autonomous pipeline manager that orchestrates the entire development workflow. You are the leader of this process.
⭐ 0· 103·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description (an autonomous pipeline manager) aligns with the SKILL.md content: the file explicitly instructs the agent to coordinate project-manager, ArchitectUX, Dev/QA loops, etc. There are no unexpected environment variables, binaries, or install steps that would be out of scope for an orchestrator.
Instruction Scope
The instructions focus on spawning and coordinating specialist agents, enforcing QA loops, retries, and reporting. They do not reference reading system files or requiring secrets, but they do instruct autonomous operation from a single command and reference a project path (project-specs/[project]-setup.md) as the launch argument. The skill is open-ended about what spawned agents may do and does not place bounds on external actions those agents might take.
Install Mechanism
No install spec and no code files — instruction-only skill. Nothing will be written to disk or downloaded by the skill itself.
Credentials
The skill requests no environment variables, credentials, or config paths. This is proportionate for an orchestration-only instruction file, though spawned agents may later request access depending on platform behavior.
Persistence & Privilege
always is false and model invocation is allowed (platform default). The skill’s design expects autonomous, multi-step orchestration after a single trigger; that grants it potentially high operational reach via spawned agents. The skill itself does not request system-level persistence, but its runtime behavior could lead to broad activity depending on platform permissions.
Assessment
This skill is internally consistent: it simply instructs an agent to act as a pipeline orchestrator and spawn other agents. It does not request credentials or install code — good. However, it is powerful: once invoked it expects to run multi-step autonomous workflows and spawn subordinate agents that (depending on your platform) might access repositories, CI, cloud resources, or create/modify artifacts. Before installing or enabling it for production: 1) verify what agent-level permissions and resource access your platform grants to spawned agents; 2) run it in a sandbox or with limited test projects first; 3) require human confirmation before granting it access to repositories, secrets, or deployment targets; 4) enable logging/audit and set resource/time quotas to limit unintended actions. If you want tighter control, ask for a variant that requires human approval at key handoffs or that explicitly limits which external systems spawned agents may contact.Like a lobster shell, security has layers — review code before you run it.
latestvk97cbn42jtt96gn4z4maq8ctbs83kd7k
License
MIT-0
Free to use, modify, and redistribute. No attribution required.