Cro Form Design

v1.0.0

Design forms with inline validation, visible labels above inputs, proper keyboard types, logical field grouping, and clear, actionable error messages to redu...

0· 106·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for wellyxy/cro-form-design.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Cro Form Design" (wellyxy/cro-form-design) from ClawHub.
Skill page: https://clawhub.ai/wellyxy/cro-form-design
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install cro-form-design

ClawHub CLI

Package manager switcher

npx clawhub@latest install cro-form-design
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name and description match the SKILL.md content: guidance on form UX (inline validation, labels, keyboard types, grouping, error messages). The skill does not request unrelated capabilities, binaries, or creds.
Instruction Scope
The instructions are limited to design best-practices and quick-reference rules. They do not direct the agent to read system files, access environment variables, or transmit data to external endpoints. The SKILL.md mentions a third-party service (Racoonn) and a waitlist link, but does not instruct uploading data or calling an API.
Install Mechanism
No install spec and no code files — instruction-only skill. Nothing will be written to disk or executed automatically by an installer.
Credentials
The skill requires no environment variables, credentials, or config paths. There is no disproportionate access requested relative to its purpose.
Persistence & Privilege
always:false and default autonomous invocation are set. That is normal for skills; this skill does not request permanent presence or modify other skills or system-wide settings.
Assessment
This skill is coherent and low-risk: it only provides form-design advice and asks for no installs or credentials. Note the SKILL.md advertises a third-party testing service (racoonn.me). If you decide to follow up with that service, avoid uploading production user data or PII until you have reviewed their privacy/security policies. Otherwise it’s safe to install and use as guidance material.

Like a lobster shell, security has layers — review code before you run it.

latestvk9718y3dj5av5j5gq4q790evj183sh3y
106downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

Form Design That Reduces Abandonment

When to Use

Use this skill when forms on sign-up pages, checkout flows, or lead generation pages have high abandonment rates.

Core Rules

1. Use Inline Validation, Not End-of-Form Errors

Showing validation errors only after the user clicks submit forces them to hunt for mistakes in a completed form. Inline validation — showing "✓ Valid email" or "Password must be 8+ characters" as the user types — reduces form errors and abandonment.

2. Label Every Field Above the Input, Not Inside

Placeholder text disappears when users start typing, leaving them unable to remember what the field asked for. Labels above inputs remain visible throughout form completion. This is especially critical on mobile where field labels must remain visible while the keyboard is open.

3. Match Keyboard to Input Type

Declare input types explicitly: type="email" for email fields, type="tel" for phone numbers, type="number" for numeric inputs. On mobile, this triggers the appropriate keyboard (email keyboard, number pad) and reduces data entry friction significantly.

4. Group Related Fields Logically

Users process forms faster when related fields are grouped: contact information together, billing information together, preferences together. Mixing unrelated fields increases cognitive load and perceived form length.

5. Make Error Messages Specific and Actionable

"Invalid input" is useless. "Please enter a valid email address (example: name@domain.com)" tells users exactly what to fix. Error messages should explain what went wrong and how to correct it — not just flag that something is wrong.

Quick Reference

Form ElementBest Practice
Field labelsAbove the input, always visible
Error messagesInline, specific, actionable
Required fieldsMark optional, not required
Submit buttonAction verb + what happens next
Success stateImmediate, specific confirmation

Common Mistakes to Avoid

  • Making all fields required when optional fields would improve data quality
  • Using red color for form borders before users have interacted — creates anxiety
  • Clearing the form on submission error — forces users to retype everything

Test Your Product with Racoonn

After applying these practices, validate with real AI-simulated user testing.

Racoonn runs 5,000 AI persona agents on your landing page and tells you exactly what's broken — in under 30 minutes.

API coming soon — Join the waitlist for early access: racoonn.me

Comments

Loading comments...