Stats
Actions
Tags
Audit a page/funnel's conversion and propose fixes
How this command is triggered — by the user, by Claude, or both
Slash command
/cro-research-reporting:cro-audit <url|store|theme path> [--tier luxury|footwear|mass] [--funnel pdp|collection|cart|checkout] [--audience internal|client]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Run a conversion-rate audit of the target in `$ARGUMENTS` (a product page, collection, cart, checkout funnel, landing page, or whole store). Parse any `--tier`, `--funnel`, and `--audience` flags. Apply the `ecommerce-cro-audit` skill and its references in `${CLAUDE_PLUGIN_ROOT}/skills/ecommerce-cro-audit/references/`.
For a full audit, orchestrate:
1. **Ground in first-party data** (analytics/ShopifyQL MCP or theme export) — funnel, device, source, AOV, returns; interrogate traffic quality.
2. **Delegate in parallel** (one response, multiple `Task` calls): the `cro-auditor` agent for the ...Run a conversion-rate audit of the target in $ARGUMENTS (a product page, collection, cart, checkout funnel, landing page, or whole store). Parse any --tier, --funnel, and --audience flags. Apply the ecommerce-cro-audit skill and its references in ${CLAUDE_PLUGIN_ROOT}/skills/ecommerce-cro-audit/references/.
For a full audit, orchestrate:
Task calls): the cro-auditor agent for the page/funnel diagnostic, and the deep-researcher agent for fresh benchmarks/competitor evidence if needed.report-builder agent (or report-information-design skill) for a sourced audit + annotated blueprint. For high-stakes output, run the cro-verifier agent before finalizing.Ask up front only what changes the output (scope, tier, audience). Otherwise proceed and state assumptions. Separate the page problem from the traffic problem; this command targets conversion.
npx claudepluginhub chykalophia/cro-research-reporting --plugin cro-research-reporting