COO Commander
v1.0.0Startup-style COO / commander role for orchestrating missions across one or more worker agents. Use when an agent must accept a business goal, break it into...
⭐ 1· 257·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 describe an orchestration/COO role and the SKILL.md contains instructions to break missions into tasks, assign work, check status, detect blockers, and close missions. There are no unrelated required binaries, env vars, or config paths.
Instruction Scope
The SKILL.md stays within orchestration scope and does not instruct the agent to read arbitrary files, access environment secrets, or send data to external endpoints. It assumes the platform provides a mechanism for assigning tasks to worker agents but does not embed any out-of-scope actions (exfiltration, system access, or hidden endpoints).
Install Mechanism
No install spec or code files are included; this is instruction-only so nothing will be written to disk or downloaded during install.
Credentials
The skill declares no required environment variables, credentials, or config paths. There are no disproportionate secret requests relative to the orchestration purpose.
Persistence & Privilege
always is false and the skill does not request elevated persistence. disable-model-invocation is false (normal), meaning the agent may invoke the skill autonomously — appropriate for an orchestrator but not excessive on its own.
Assessment
This skill appears to be a straightforward coordinator that does not request credentials or install software. Before installing, consider whether you trust the agent (and any worker agents it will coordinate) to act autonomously: orchestration can cause other agents to perform actions on your behalf. Limit worker-agent privileges, review logs/decisions during initial tests, and consider disabling autonomous invocation if you want manual approval for each mission. If you use worker skills that require credentials, ensure those credentials are scoped and audited — the COO Commander itself does not request them, but it will direct workers that might.Like a lobster shell, security has layers — review code before you run it.
latestvk97fytrbmv2s3c5q9295ngdg3d82qyr0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.