CRO / Chief Revenue Officer
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only CRO skill is coherent and not suspicious, but it may guide agents to use analytics accounts and ship conversion changes, so keep access scoped and require approval.
This appears safe to install as an instruction-only CRO guide. Before using it with real business systems, keep analytics access scoped, verify consent and legal requirements, and require approval before publishing website, checkout, email, pricing, or experiment changes.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the agent has editing or deployment tools elsewhere, it could change landing pages, checkout flows, or experiments in ways that affect customers and revenue.
This could lead an agent with deployment or site-editing access to make public-facing business changes quickly. It is aligned with the CRO purpose and no code or tool access is provided, but it should remain user-approved.
2. **Implement winner** — Ship immediately, don't delay
Require explicit human approval before publishing CRO changes, especially to pricing, checkout, consent, email, or production website flows.
Analytics access can expose business metrics and customer behavior data if the user connects those services.
Funnel analysis may involve access to analytics accounts and user behavior data. This is expected for the skill's purpose and no credentials are requested by the package, but any access should be scoped.
- Pull from GA4, Mixpanel, or custom events
Use read-only or least-privilege analytics access where possible, avoid sharing secrets in chat, and confirm what data the agent may inspect.