COO / Chief Operations Officer
v1.0.2Be the COO with process design, organizational scaling, cross-functional execution, and operational excellence.
⭐ 6· 1.5k·3 current·3 all-time
byIván@ivangdavila
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 (COO: process design, scaling, execution, metrics) align with the included markdown files (process.md, scaling.md, execution.md, metrics.md). There are no unexpected binaries, environment variables, or config paths requested.
Instruction Scope
SKILL.md and the supporting files contain templates, checklists, and frameworks for operational decision-making. They do not instruct the agent to read unrelated files, call external services, or exfiltrate data. The guidance explicitly states no external API calls and no persistent storage; the skill is instruction-only so there is no embedded code to perform other actions.
Install Mechanism
No install spec or code files are present — this is an instruction-only skill, which minimizes surface area (nothing is downloaded or written to disk by the skill package itself).
Credentials
The skill requires no environment variables or credentials. There are no requests for tokens, keys, or system configuration, which is proportionate for a strategy/advice skill.
Persistence & Privilege
Flags are default (always: false, user-invocable: true, model invocation allowed). The skill does not request permanent presence or modify other skills' configurations. Autonomous invocation is permitted by platform default but the skill content itself does not grant extra privileges.
Assessment
This skill is coherent and appears safe to install: it is an instruction-only COO advisor with no network calls, no credentials requested, and no install actions. Before enabling, consider: (1) the agent may act autonomously per platform defaults — keep human oversight enabled for high‑stakes org decisions (hiring, firing, vendor contracts, restructures); (2) do not paste sensitive or personally identifying data into prompts if you want to avoid storing that information elsewhere; (3) if the skill suggests installing related skills (clawhub commands), review those skills separately before installing them. If you want extra caution, disable autonomous invocation for this skill or require explicit user approval before any action.Like a lobster shell, security has layers — review code before you run it.
latestvk97854wfxpvhhyz80tyt061cas81f3s8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
⚡ Clawdis
OSLinux · macOS · Windows
