checkout-cro
Skill0 starsChanged 53 days agoLicence not identifiedView on GitHub
When the user wants to audit or improve an e-commerce cart or checkout — including checkout abandonment, cart abandonment, low checkout completion rate, revenue per visitor, or average order value. Also use when the user says 'checkout audit,' 'checkout CRO,' 'people abandon at checkout,' 'my cart abandonment is high,' 'nobody completes the purchase,' 'optimize my Shopify checkout,' 'improve our payment page,' 'should we add express checkout,' 'is our coupon field hurting us,' or 'should we upsell at checkout.' Use this even if the user just shares a store URL and asks for feedback on the buying experience. For marketing pages before the cart, see cro. For SaaS registration flows, see signup. To run the tests this audit produces, see ab-testing.
In this repository105 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- 14-day-change-controlSkill
- ab-testingSkill
- ad-copy-auditSkill
- ad-creativeSkill
- ad-headline-techniquesSkill
- ad-library-extractionSkill
- ads-campaign-planningSkill
- advantage-plus-auditSkill
- ad-writing-styleSkill
- agent-routingSkill
- analyticsSkill
- attributionSkill
- audience-insights-miningSkill
- audit-artifactsSkill
- audit-preflightSkill
- bid-strategy-and-learningSkill
- browser-inspectionSkill
- business-contextSkill
- cac-and-roasSkill
- campaign-rcaSkill
- capi-and-emqSkill
- catalog-healthSkill
- competitor-profilingSkill
- conflict-resolutionSkill
- contribution-marginSkill
- copy-editingSkill
- copywritingSkill
- coverage-ledgerSkill
- creative-angle-analysisSkill
- creative-cadence-operating-systemSkill
- creative-dashboardSkill
- creative-data-modelSkill
- creative-fatigue-detectionSkill
- creative-taxonomySkill
- creative-testing-engineSkill
- creative-to-page-continuitySkill
- cro-experiment-designSkill
- croSkill
- cross-source-reconciliationSkill
- customer-researchSkill
- data-cacheSkill
- delivery-diagnosticsSkill
- demand-lifecycleSkill
- ecommerce-measurementSkill
- emailsSkill
- frequency-and-saturationSkill
- full-auditSkill
- funnel-analysisSkill
- ga4-extractionSkill
- homepage-croSkill
- incrementalitySkill
- lead-capture-optimizationSkill
- leading-and-lagging-signalsSkill
- learning-phase-and-significanceSkill
- link-trackingSkill
- marketing-psychologySkill
- mcp-discoverySkill
- message-validationSkill
- meta-ads-data-validationSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 15 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈15
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

