This is the front door to the CRO, research & reporting toolkit. Use it FIRST when someone is getting started, is unsure which skill to use, or makes a broad/vague request. Trigger phrases: "where do I start", "what can this do", "how do I use this", "get started", "set up", "onboard me", "help me with my store/page/campaign", "what should I focus on", "I don't know where to begin". It orients the user, captures a reusable engagement brief, and routes to the right skill, command, or agent.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cro-research-reporting:getting-startedThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The front door. Orient the user, capture a reusable engagement brief, then route to the right tool. Run this whenever someone is starting, is unsure which skill applies, or asks something broad.
The front door. Orient the user, capture a reusable engagement brief, then route to the right tool. Run this whenever someone is starting, is unsure which skill applies, or asks something broad.
A strategist's kit to: audit a conversion funnel, run deep sourced research, write conversion copy, sharpen positioning/outbound, and turn it into polished reports + redesign blueprints — with a verifier that checks the work before it ships.
Before doing real work, establish the shared context every other skill reads first.
./cro-engagement.md (the default; or ask the user for the path). If present, read it, summarize it back in 2–3 lines, and ask if anything changed.references/engagement-brief-template.md:
./cro-engagement.md from the template. Keep it short and current; confirm before overwriting.Why: the skills are most powerful when they share one context (so they stop re-asking and stay consistent). This is the coherence layer for the whole suite.
Match the user's intent to a component using references/routing-map.md. Quick version:
ecommerce-cro-audit skill (it can delegate to the cro-auditor agent).deep-research-synthesis (fans out deep-researcher agents).report-information-design (or the report-builder agent).conversion-copywriting.outbound-and-positioning.cro-verifier agent.For a full engagement, the canonical path is: Brief (this skill) → /cro-audit (grounds in data, fans out research + page diagnostic) → /build-report (assemble) → cro-verifier (pre-ship check) → conversion-copywriting / outbound-and-positioning for the language. Offer to kick off the first step.
references/engagement-brief-template.md — the brief template, field definitions, where it lives, and update cadence.references/routing-map.md — full intent → skill/command/agent map and the end-to-end playbook.Don't interrogate the user — ask only the brief questions that matter for the task at hand, and infer the rest. Don't overwrite an existing brief without confirming. If the user clearly already knows what they want, skip the orientation and route straight there.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub chykalophia/cro-research-reporting --plugin cro-research-reporting