AGENT SKILL

form-cro

When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.

License 许可
MIT
所属仓库
msm47/Gitskil
最近更新
2026-06-22
Stars
★ 0
Forks
0

01 前言 Front Matter

name
form-cro
license
MIT
metadata
{ "author": "Alireza Rezvani", "updated": 1772755200000, "version": "1.0.0", "category": "marketing" }
description
When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.

02 资源文件 2

03 SKILL.md 正文

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

Check for product marketing context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before providing recommendations, identify:

  1. Form Type

    • Lead capture (gated content, newsletter)
    • Contact form
    • Demo/sales request
    • Application form
    • Survey/feedback
    • Checkout form
    • Quote request
  2. Current State

    • How many fields?
    • What's the current completion rate?
    • Mobile vs. desktop split?
    • Where do users abandon?
  3. Business Context

    • What happens with form submissions?
    • Which fields are actually used in follow-up?
    • Are there compliance/legal requirements?

Core Principles

→ See references/form-cro-playbook.md for details

Output Format

Form Audit

For each issue:

  • Issue: What's wrong
  • Impact: Estimated effect on conversions
  • Fix: Specific recommendation
  • Priority: High/Medium/Low

Recommended Form Design

  • Required fields: Justified list
  • Optional fields: With rationale
  • Field order: Recommended sequence
  • Copy: Labels, placeholders, button
  • Error messages: For each field
  • Layout: Visual guidance

Test Hypotheses

Ideas to A/B test with expected outcomes


Experiment Ideas

Form Structure Experiments

Layout & Flow

  • Single-step form vs. multi-step with progress bar
  • 1-column vs. 2-column field layout
  • Form embedded on page vs. separate page
  • Vertical vs. horizontal field alignment
  • Form above fold vs. after content

Field Optimization

  • Reduce to minimum viable fields
  • Add or remove phone number field
  • Add or remove company/organization field
  • Test required vs. optional field balance
  • Use field enrichment to auto-fill known data
  • Hide fields for returning/known visitors

Smart Forms

  • Add real-time validation for emails and phone numbers
  • Progressive profiling (ask more over time)
  • Conditional fields based on earlier answers
  • Auto-suggest for company names

Copy & Design Experiments

Labels & Microcopy

  • Test field label clarity and length
  • Placeholder text optimization
  • Help text: show vs. hide vs. on-hover
  • Error message tone (friendly vs. direct)

CTAs & Buttons

  • Button text variations ("Submit" vs. "Get My Quote" vs. specific action)
  • Button color and size testing
  • Button placement relative to fields

Trust Elements

  • Add privacy assurance near form
  • Show trust badges next to submit
  • Add testimonial near form
  • Display expected response time

Form Type-Specific Experiments

Demo Request Forms

  • Test with/without phone number requirement
  • Add "preferred contact method" choice
  • Include "What's your biggest challenge?" question
  • Test calendar embed vs. form submission

Lead Capture Forms

  • Email-only vs. email + name
  • Test value proposition messaging above form
  • Gated vs. ungated content strategies
  • Post-submission enrichment questions

Contact Forms

  • Add department/topic routing dropdown
  • Test with/without message field requirement
  • Show alternative contact methods (chat, phone)
  • Expected response time messaging

Mobile & UX Experiments

  • Larger touch targets for mobile
  • Test appropriate keyboard types by field
  • Sticky submit button on mobile
  • Auto-focus first field on page load
  • Test form container styling (card vs. minimal)

Task-Specific Questions

  1. What's your current form completion rate?
  2. Do you have field-level analytics?
  3. What happens with the data after submission?
  4. Which fields are actually used in follow-up?
  5. Are there compliance/legal requirements?
  6. What's the mobile vs. desktop split?

Related Skills

  • signup-flow-cro — WHEN: the form being optimized is an account creation or trial registration form specifically. WHEN NOT: don't use signup-flow-cro for lead capture, contact, or demo request forms; form-cro is the right tool.
  • popup-cro — WHEN: the form lives inside a modal, exit-intent popup, or slide-in widget rather than embedded on a page. WHEN NOT: don't use popup-cro for standalone page-embedded forms.
  • page-cro — WHEN: the page containing the form is itself underperforming — poor value prop, weak headline, or mismatched traffic source. Fix the page context before or alongside the form. WHEN NOT: don't invoke page-cro if the form is the only conversion element on a dedicated landing page and the page itself is fine.
  • ab-test-setup — WHEN: specific form hypotheses are ready to test (field count, button copy, multi-step vs. single-step). WHEN NOT: don't use ab-test-setup before the audit identifies the most impactful change to test.
  • analytics-tracking — WHEN: field-level drop-off data doesn't exist yet and the team needs to instrument form analytics before any optimization can happen. WHEN NOT: skip if analytics are already in place.
  • marketing-context — WHEN: check .claude/product-marketing-context.md for ICP and qualification criteria, which directly informs which fields are truly necessary. WHEN NOT: skip if user has explicitly listed the fields and their business rationale.

Communication

All form CRO output follows this quality standard:

  • Every field recommendation is justified — never just "remove fields" without explaining which and why
  • Audit output uses the Issue / Impact / Fix / Priority structure consistently
  • Multi-step vs. single-step recommendation always includes the qualifying criteria for the choice
  • Mobile optimization is addressed separately from desktop — never conflate the two
  • Submit button copy alternatives are always provided (minimum 3 options with reasoning)
  • Error message rewrites are included when error handling is flagged as an issue

Proactive Triggers

Automatically surface form-cro when:

  1. "Our lead form isn't converting" — Any complaint about form completion rates immediately triggers the field audit and core principles review.
  2. Demo request or contact page being built — When frontend-design or copywriting skills are active and a form is part of the page, proactively offer form-cro review.
  3. "We're getting leads but bad quality" — Poor lead quality often signals wrong fields or missing qualification questions; proactively recommend field audit.
  4. Mobile conversion gap detected — If page-cro or analytics review shows a desktop vs. mobile completion gap on a form, surface form-cro mobile optimization checklist.
  5. Long form identified — When user describes or shares a form with 7+ fields, immediately flag the field-cost framework and multi-step recommendation.

Output Artifacts

Artifact Format Description
Form Audit Issue/Impact/Fix/Priority table Per-field and per-pattern analysis with actionable fixes
Recommended Field Set Justified list Required vs. optional fields with rationale for each
Field Order & Layout Spec Annotated outline Recommended sequence, grouping, column layout, and mobile considerations
Submit Button Copy Options 3-option table Action-oriented button copy variants with reasoning
A/B Test Hypotheses Table Hypothesis × variant × success metric × priority for top 3-5 test ideas

04 同仓库更多 Skills

msm47
msm47/Gitskil

syllabus

Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.

★ 0
msm47
msm47/Gitskil

research

Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — "research [topic]", "look into [topic]", "what do we know about [topic]", "investigate [topic]", "find me information on [topic]", "do some research on [topic]", "I need to understand [topic]", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.

★ 0
msm47
msm47/Gitskil

pulse

Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.

★ 0
msm47
msm47/Gitskil

patent

Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.

★ 0
msm47
msm47/Gitskil

notebooklm

Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.

★ 0
msm47
msm47/Gitskil

litreview

Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.

★ 0