contact-page-generator

When the user wants to create, optimize, or audit contact page and forms. Also use when the user mentions "contact page," "contact form," "get in touch," "support form," "contact us," "reach us," "contact information," "support contact," or "inquiry form." For sitewide page planning, use website-structure.

Safety Notice

This listing is from the official public ClawHub registry. Review SKILL.md and referenced scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "contact-page-generator" with this command: npx skills add kostja94/contact-page-generator

Pages: Contact

Guides contact page design and form optimization for conversions.

When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for brand voice.

Identify:

  1. Contact types: Sales, support, general, press
  2. Form purpose: Lead capture, support ticket, demo request
  3. Alternative channels: Email, phone, chat, social

Best Practices

Form Design

PrincipleGuideline
Short3-5 fields for basic contact; long forms increase abandonment
Single columnVertical layout; works better on mobile
Logical groupingName+email together; address fields together
Required fieldsMark clearly (asterisk); avoid surprises
Progressive disclosureShow relevant fields based on selections

Field Labels

  • Clear language: "Email Address" not "Email ID"
  • Conversational: Friendly, welcoming
  • No jargon: Universally understood terms

CTA Button

  • Action verbs: "Send Message," "Get in Touch," "Start a Conversation"
  • Avoid generic: "Submit" ? "Send Message"
  • Stand out: Contrasting color, clear hierarchy

Page-Level

ElementGuideline
Visibility"Contact" or "Support" in main nav, not just footer
MobileAppropriate input types (tel for phone), large tap targets
ProofreadingNo typos--credibility at conversion moment
AlternativesEmail, phone, chat if form isn't right

Trust

  • Response time: "We reply within 24 hours"
  • Privacy: Link to privacy policy near form
  • Security: HTTPS, visible trust signals

Output Format

  • Form structure (fields, order)
  • Copy (labels, placeholder, CTA)
  • Page layout and placement
  • SEO metadata
  • Accessibility checklist

Related Skills

  • landing-page-generator: Lead capture LP contains contact form; demo request CTA destination
  • about-page-generator: Contact often linked from About
  • legal-page-generator: Privacy policy link near form
  • title-tag, meta-description, page-metadata: Contact page metadata

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Security

Tophant Clawvault Operator

Operate ClawVault services, configuration, vault presets, and scanning from OpenClaw

Registry SourceRecently Updated
Security

review-sendmsg

Perform detailed Python code reviews identifying bugs, security risks, test gaps, and maintainability issues in diffs, patches, or pull requests.

Registry SourceRecently Updated
Security

Trent OpenClaw Security Assessment

Assess your Agent deployment against security risks using Trent.

Registry SourceRecently Updated
Security

X402 Cfo

Financial brain for x402 payments — budget enforcement, cost policies, spend analytics, anomaly detection, and audit trail for autonomous agents.

Registry SourceRecently Updated