Cro Checkout
v1.0.0Optimize checkout by offering guest checkout, showing total costs early, adding trust signals, minimizing steps, and sending quick abandon cart emails.
⭐ 0· 49·0 current·0 all-time
by@wellyxy
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description (CRO/checkout optimization) match the SKILL.md content: UX recommendations, shipping/tax transparency, trust signals, guest checkout, and abandoned-cart follow-up. The skill does not request unrelated credentials or binaries.
Instruction Scope
SKILL.md contains non-executable advice and recommendations for UI/UX and email follow-up. It does not instruct the agent to read system files, access environment variables, call external endpoints, or execute commands. The only external reference is a marketing link to racoonn and a claim about an API coming soon — but no runtime steps call it.
Install Mechanism
No install spec and no code files — instruction-only. Nothing is downloaded or written to disk by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths; its guidance (UI copy, placement, timings) doesn’t justify additional secrets or system access.
Persistence & Privilege
always is false and the skill does not request permanent presence or to modify other skills/config. Default autonomous invocation is allowed but the skill’s instructions are passive guidance, not autonomous actions that access external resources.
Assessment
This skill is essentially a written checklist and is internally coherent — it doesn’t ask for any system access or install anything. Before installing/using it: (1) Note the racoonn reference is marketing (external site) — do not assume the skill will integrate with any external API unless a later version adds explicit install/credentials; review any future update that adds network calls or env var requirements. (2) If you implement the recommended abandoned-cart emails, ensure you have user consent and comply with spam and privacy laws (GDPR, CAN-SPAM, etc.). (3) Follow PCI and payment-data best practices when changing payment forms (do not capture or transmit card data unless using a PCI-compliant provider). (4) Treat the percentage 'lifts' as estimates; A/B test changes rather than rolling them site-wide. (5) Monitor future versions for added install steps, downloads, or credential requests — those would change this assessment.Like a lobster shell, security has layers — review code before you run it.
latestvk975a3mtcnyyk8rnmfgp4jkv2983scd6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.