Form CRO
v1.0.0Optimise form completion by analysing fields, reducing unnecessary inputs, restructuring steps, improving UX, and recommending A/B tests for better conversion.
⭐ 1· 88·0 current·0 all-time
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 match the instructions: analysing form fields, reducing inputs, restructuring steps, and recommending A/B tests. Nothing requested (no env vars, no binaries, no installs) is inconsistent with a UX/CRO advisory skill.
Instruction Scope
The SKILL.md tells the agent to 'Analyse: current fields, completion rate, drop-off points' but does not specify how to obtain metrics or analytics data; the skill is silent about whether the agent should ask the user for analytics exports, connect to an analytics provider, or infer from provided markup. This is a clarity/usability gap rather than a security incoherence—agent should explicitly request user-provided form specs and metrics before making quantitative recommendations.
Install Mechanism
Instruction-only skill with no install steps or downloaded artifacts. This is low risk and consistent with the described functionality.
Credentials
No environment variables, credentials, or config paths are required. That is proportionate to an advisory/form-design skill which should operate on user-provided form descriptions or exported metrics.
Persistence & Privilege
Skill is not set to always:true and does not request persistent system presence or modification of other skills. Autonomous invocation is allowed by platform default but is not combined with other elevated privileges.
Assessment
This skill is coherent and low-risk because it only contains instructions and asks for no credentials or installs. Before using it: (1) be prepared to provide form structure and any analytics exports (completion rates, drop-off points); the skill does not itself connect to analytics services or request credentials, so grant access deliberately if needed; (2) avoid pasting real user PII when sharing form examples—anonymise data; (3) treat the statistics and 'key principles' as heuristics: validate A/B recommendations in your environment before deployment; (4) if you want the agent to access analytics directly, require explicit instructions and verify which credentials it will request.Like a lobster shell, security has layers — review code before you run it.
conversionvk970d8egdgn1rh4sexbcmbjchh83a41zcrovk970d8egdgn1rh4sexbcmbjchh83a41zlatestvk970d8egdgn1rh4sexbcmbjchh83a41z
License
MIT-0
Free to use, modify, and redistribute. No attribution required.