ClawHub

CGO / Chief Growth Officer

v1.0.1

Drive systematic growth with acquisition loops, experimentation frameworks, retention systems, and product-led strategies.

⭐ 4· 879·1 current·1 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description (Chief Growth Officer guidance) match the content (acquisition, retention, experiments, metrics). The skill requests no binaries, env vars, or config access—consistent with a purely advisory skill.
✓
Instruction Scope
SKILL.md and the included docs are prescriptive guidance for growth leadership only. They do not instruct the agent to read local files, access credentials, exfiltrate data, or contact unknown endpoints. Mentions of 'clawhub' are benign install/feedback commands for related skills and do not imply hidden behavior.
✓
Install Mechanism
No install spec and no code files — the skill is instruction-only, so nothing is downloaded or written to disk. This is the lowest-risk install profile.
✓
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. That is proportionate for a guidance/consulting skill.
✓
Persistence & Privilege
Flags show normal defaults (always: false, user-invocable: true, model invocation allowed). There is no request for permanent presence or elevated privileges and the skill does not attempt to modify other skills or system settings.
Assessment
This skill is low-risk: it's a text-only growth playbook. Before installing or acting on its advice, remember: 1) related skills linked in the doc (e.g., analytics, cmo) may require API keys or access—review their SKILL.md before installing; 2) advice here is strategic, not an automated action plan—do not give any credentials or run external install commands (like clawhub install) without verifying the target skill; 3) when the agent suggests operational changes (e.g., instrumentation, experiments), validate with your engineers and limit any credentials or tokens to least privilege.

Like a lobster shell, security has layers — review code before you run it.

latestvk978rv3ax8w6tyxbcejycmgqv981h60z

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

📈 Clawdis
OSLinux · macOS · Windows

Comments