A guide for improving forms that are not account sign-up forms, such as contact, lead-capture, demo-request, application, survey, quote, and checkout forms. It focuses on making forms easier to complete while retaining useful information.

It is for reviewing field counts, completion and abandonment problems, mobile-versus-desktop behavior, form wording, and the information each field truly needs to collect.

It helps identify unnecessary fields, unclear value, and other sources of abandonment. The aim is to reduce effort without losing information needed for follow-up or processing.

form-cro — Skill for Claude Code and Codex by Orkas-AI

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add Orkas-AI/Orkas-Awesome-AgentSkills --skill form-cro

Clone the repo

git clone --depth 1 https://github.com/Orkas-AI/Orkas-Awesome-AgentSkills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/orkas-ai/orkas-awesome-agentskills/form-cro/github.svg)](https://agentmods.dev/skills/orkas-ai/orkas-awesome-agentskills/form-cro)

Your own site

<a href="https://agentmods.dev/skills/orkas-ai/orkas-awesome-agentskills/form-cro"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas-awesome-agentskills/form-cro/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/orkas-ai/orkas-awesome-agentskills/form-cro"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas-awesome-agentskills/form-cro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,405 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00097	$0.02405
Opus 5	$0.00048	$0.01203
Sonnet 5	$0.00019	$0.00481
Haiku 4.5	$0.00010	$0.00241

Measured 12d ago against content hash 0d41e83de986, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

form-cro scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to form-cro — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

product/skills/marketing-skills/references/form-cro/SKILL.md · 426 lines

How it starts

The opening of the file, as written. The whole thing — 426 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Form CRO

You are an expert in form optimization. Your goal is to maximize form completion rates while capturing the data that matters.

Initial Assessment

Before providing recommendations, identify:

Form Type
- Lead capture (gated content, newsletter)
- Contact form
- Demo/sales request
- Application form
- Survey/feedback
- Checkout form
- Quote request
Current State
- How many fields?
- What's the current completion rate?
- Mobile vs. desktop split?
- Where do users abandon?
Business Context
- What happens with form submissions?
- Which fields are actually used in follow-up?
- Are there compliance/legal requirements?

Core Principles

1. Every Field Has a Cost

Each field reduces completion rate. Rule of thumb:

3 fields: Baseline
4-6 fields: 10-25% reduction
7+ fields: 25-50%+ reduction

For each field, ask:

Is this absolutely necessary before we can help them?
Can we get this information another way?
Can we ask this later?

2. Value Must Exceed Effort

Clear value proposition above form
Make what they get obvious
Reduce perceived effort (field count, labels)

3. Reduce Cognitive Load

One question per field
Clear, conversational labels
Logical grouping and order
Smart defaults where possible

Field-by-Field Optimization

Email Field

Single field, no confirmation
Inline validation
Typo detection (did you mean gmail.com?)
Proper mobile keyboard

Name Fields

Single "Name" vs. First/Last — test this
Single field reduces friction
Split needed only if personalization requires it

Phone Number

Make optional if possible
If required, explain why
Auto-format as they type
Country code handling

Company/Organization

Auto-suggest for faster entry
Enrichment after submission (Clearbit, etc.)
Consider inferring from email domain

Job Title/Role

Dropdown if categories matter
Free text if wide variation
Consider making optional

Read the full file on GitHub · 426 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

12d ago First seen · 426 lines · 97 tokens per session scan A 0d41e83de986

Subscribe to this mod's changes

form-cro is a skill published in the GitHub repository Orkas-AI/Orkas-Awesome-AgentSkills (13 stars, last pushed 2mo ago), licensed MIT. It adds 97 tokens to every session and 2,405 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to form-cro, differing in 0 lines, and is treated as a copy.

Marketing and SEO agent-framework agent-skills ai-agents ai-tools automation awesome-list

viral-tech-reel-editor

End-to-end viral tech reel production for Instagram Reels and TikTok using 2026 trend grammar — retention-first pacing, punch-ins, 3D cinematic AI-generated shots, motion design graphics, proof b-roll, trending SFX, karaoke captions (Georgian/English), safe-zone layout, and QA-gated 1080x1920 export. This skill should…

tornikebolokadze1-cyber/awesome-ai-pulse-georgia · 172 tokens

implementing-aws-config-rules-for-compliance

Implementing AWS Config rules for continuous compliance monitoring of AWS resources, deploying managed and custom rules aligned to CIS and PCI DSS frameworks, configuring automatic remediation with SSM Automation, and aggregating compliance data across accounts.

adriannoes/awesome-agentic-ai · 53 tokens

hive.chart-creation-foundations

Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…

aden-hive/hive · 133 tokens

form-cro