Contact Page Generator
Design or audit a contact page and form so leads and support inquiries convert without unnecessary fields.
Overview
contact-page-generator is an agent skill most often used in Validate (also Launch, Grow) that designs and optimizes contact pages and forms for conversions.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill contact-page-generatorWhat is this skill?
- Initial assessment for sales, support, general, and press contact types
- Form design table: 3–5 fields, single column, progressive disclosure
- Reads .claude/project-context.md or .cursor/project-context.md for brand voice when present
- Pairs with website-structure for sitewide page planning
- Field grouping and required-field clarity guidelines for mobile-first layouts
- Recommends 3–5 fields for basic contact forms
- Skill metadata version 1.0.1
Adoption & trust: 763 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your contact page is either missing, too long, or unclear about sales versus support, so visitors abandon before reaching you.
Who is it for?
Founders launching or refreshing a marketing site who need a credible contact or support form without hiring a conversion specialist.
Skip if: Full sitewide IA or URL policy—use website-structure or url-structure skills for those scopes.
When should I use this skill?
User wants to create, optimize, or audit contact pages and forms, or mentions contact page, contact form, get in touch, or inquiry form.
What do I get? / Deliverables
You get form structure, field guidance, and channel recommendations aligned to your contact types and brand context file when available.
- Contact page structure recommendation
- Form field and layout specification
- Channel mix for sales, support, press, and general inquiries
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Validate/landing is the shelf for pages that prove the offer and capture intent before full product scale. Contact pages are core landing assets for demo requests, support, and lead capture tied to conversion testing.
Where it fits
Scope a 4-field demo request form with sales versus support routing on your pre-launch landing page.
Add press and partnership contact blocks with alternative email and social channels.
Shorten an overloaded support form and group address fields for mobile abandonment fixes.
How it compares
Focused page-and-form playbook, not a full CMS or ticketing integration.
Common Questions / FAQ
Who is contact-page-generator for?
Solo builders and indie SaaS founders who own their marketing site and need practical contact-page and form guidance.
When should I use contact-page-generator?
In Validate when building a landing contact page; at Launch when polishing distribution touchpoints; in Grow when improving support and lead capture flows.
Is contact-page-generator safe to install?
It is documentation-style guidance; confirm vendor trust via the Security Audits panel on this Prism page before adding to your agent.
SKILL.md
READMESKILL.md - 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 | Principle | Guideline | |-----------|-----------| | **Short** | 3-5 fields for basic contact; long forms increase abandonment | | **Single column** | Vertical layout; works better on mobile | | **Logical grouping** | Name+email together; address fields together | | **Required fields** | Mark clearly (asterisk); avoid surprises | | **Progressive disclosure** | Show 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 | Element | Guideline | |---------|-----------| | **Visibility** | "Contact" or "Support" in main nav, not just footer | | **Mobile** | Appropriate input types (tel for phone), large tap targets | | **Proofreading** | No typos--credibility at conversion moment | | **Alternatives** | Email, 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