Skip to content
Back to skills

003 Name Skill Ddea7b79

ASecurity

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," or "support form."

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
content-marketingrustgosecurity

Works with

  • cursor

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 003-name-skill_ddea7b79 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 003 Name Skill Ddea7b79?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 003 Name Skill Ddea7b79
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-003-name-skill-ddea7b79/badge)](https://www.skillsdirectory.com/skills/tools-only-003-name-skill-ddea7b79)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
---
name: pages-contact
description: 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," or "support form."
metadata:
  version: 1.0.0
---

# 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 product marketing context first:** If `.claude/product-marketing-context.md` or `.cursor/product-marketing-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

- **pages-about**: Contact often linked from About
- **pages-legal**: Privacy policy link near form
- **seo-on-page-title, seo-on-page-description, seo-on-page-metadata**: Contact page metadata

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.