← Back to Skills Marketplace
1157
Downloads
6
Stars
4
Active Installs
2
Versions
Install in OpenClaw
/install cro
Description
Optimize conversion rates with funnel analysis, A/B testing, statistical significance, and compliance-safe experiments.
README (SKILL.md)
When to Use
User wants to improve conversion rates for websites, landing pages, SaaS products, or eCommerce. Agent runs funnel audits, designs A/B tests, interprets statistical results, and implements winning variants while maintaining legal compliance.
Quick Reference
| Topic | File |
|---|---|
| A/B testing methodology | testing.md |
| Conversion audits | audits.md |
| Legal compliance | legal.md |
| Tools and integrations | tools.md |
Core Rules
1. Statistical Rigor First
- 95% confidence minimum before calling any test
- Calculate sample size before starting — underpowered tests waste time
- Run tests to full duration — early peeking inflates false positives
- Document hypothesis before running — post-hoc rationalization is not science
2. Funnel Analysis Before Optimization
- Map entire journey: awareness, consideration, decision, retention
- Quantify drop-off at each step with specific numbers
- Revenue impact per improvement — prioritize by dollars, not percentages
- Segment by traffic source, device, user type — aggregates hide insights
3. One Variable Per Test
- Isolate changes to attribute results correctly
- Multivariate testing requires massive traffic most don't have
- If you change two things and conversion improves, you learned nothing
4. Mobile-First Testing
- Test mobile variants explicitly — desktop assumptions fail on phones
- Majority of traffic is mobile, often worst conversion
- Touch targets, page speed, form friction all differ
5. Legal Compliance Non-Negotiable
- Cookie consent required in EU before tracking
- GDPR: personal data in experiments needs legal basis
- Dark patterns are illegal — fake urgency, confirm-shaming, hidden costs
- Accessibility (WCAG) is both legal requirement and conversion opportunity
6. Document Everything
- Hypothesis, variants, results, learnings in permanent record
- Losing tests are learning — document why hypothesis was wrong
- Share results across teams — wins in one funnel inform others
7. Revenue Connection
- Revenue targets tie to conversion targets — make the math explicit
- Signups mean nothing if they never convert to revenue
- Prioritize by ICE: Impact, Confidence, Ease
Common Traps
- Calling tests early because results look good — false positives waste resources
- "We changed everything and revenue went up" — no control group proves nothing
- Copy-pasting competitor tactics without context — what works for them may fail for you
- Optimizing for vanity metrics — engagement without revenue is vanity
- Testing without proper tracking setup — retroactive data is unreliable
Related Skills
Install with clawhub install \x3Cslug> if user confirms:
ceo— strategic leadershipcfo— financial planningcmo— marketing strategyanalytics— data analysis
Feedback
- If useful:
clawhub star cro - Stay updated:
clawhub sync
Usage Guidance
This skill is an advisory, instruction-only CRO playbook and appears coherent. Before installing or letting an agent act on its recommendations: 1) Be cautious about granting any agent access to production systems — only supply minimal, scoped API keys (read-only where possible) and rotate them regularly. 2) If you allow the agent to 'implement' changes, require human approval and run changes on staging first. 3) Follow the legal.md guidance for EU/CA consent rules — do not run experiments that rely on cookies/identifiers without proper consent. 4) Log and document all tests and data sources (the skill emphasizes this; enforce it operationally). 5) If you integrate third-party tools, prefer official SDKs/APIs and audit their scopes; the skill itself does not include any downloads or hidden endpoints, so risk comes from granting access to external systems, not from the skill's content.
Capability Analysis
Type: OpenClaw Skill
Name: cro
Version: 1.0.1
The skill bundle provides comprehensive documentation and guidelines for Conversion Rate Optimization (CRO). All files (`_meta.json`, `SKILL.md`, `audits.md`, `legal.md`, `testing.md`, `tools.md`) contain only informational text, best practices, and illustrative examples relevant to CRO. There are no executable code snippets, shell commands, network calls, or file system operations embedded in the markdown that could be exploited. No evidence of prompt injection attempts, data exfiltration, persistence mechanisms, or any other malicious intent was found.
Capability Assessment
Purpose & Capability
Name/description (conversion optimization, A/B testing, funnel audits) match the included guidance (audits.md, testing.md, tools.md, legal.md). References to analytics and experimentation platforms (GA4, Mixpanel, Optimizely, etc.) are appropriate for the stated purpose.
Instruction Scope
SKILL.md and supporting files limit the agent to audit, test design, statistical interpretation, compliance guidance, and recommended actions. There are no instructions to read unrelated system files, exfiltrate data, or call external endpoints outside of listing common third-party tools. The only operational ambiguity: 'implement winning variants' implies making changes/deploys, but the skill doesn't include automated deploy/install instructions or credentials—so the scope remains advisory.
Install Mechanism
No install spec and no code files — instruction-only. This is low-risk: nothing is downloaded or written to disk by the skill itself.
Credentials
The skill itself requests no environment variables or credentials (which is proportionate). In practice, using the recommended integrations will require API keys or access to analytics/experimentation platforms; the skill does not request or store these. Users should provide only minimal-scope credentials if they plan to let an agent take actions.
Persistence & Privilege
always is false and there is no install that persists components. The skill does not request elevated or system-wide privileges and does not modify other skills' configs. Autonomous invocation is enabled (platform default) but poses no additional incoherence by itself.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install cro - After installation, invoke the skill by name or use
/cro - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
Added Core Rules structure with statistical rigor and compliance guidelines.
v1.0.0
Initial release
Metadata
Frequently Asked Questions
What is CRO / Chief Revenue Officer?
Optimize conversion rates with funnel analysis, A/B testing, statistical significance, and compliance-safe experiments. It is an AI Agent Skill for Claude Code / OpenClaw, with 1157 downloads so far.
How do I install CRO / Chief Revenue Officer?
Run "/install cro" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is CRO / Chief Revenue Officer free?
Yes, CRO / Chief Revenue Officer is completely free (open-source). You can download, install and use it at no cost.
Which platforms does CRO / Chief Revenue Officer support?
CRO / Chief Revenue Officer is cross-platform and runs anywhere OpenClaw / Claude Code is available (linux, darwin, win32).
Who created CRO / Chief Revenue Officer?
It is built and maintained by Iván (@ivangdavila); the current version is v1.0.1.
More Skills