/contact
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
$ npx -y skills add kostja94/marketing-skills --skill contact --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/contact
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
contact.SKILL.mdname: contact-page-generator
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," "support form," "contact us," "reach us," "contact information," "support contact," or "inquiry form." For sitewide page planning, use website-structure.
metadata:
version: 1.0.1
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
Read more
name: contact-page-generator 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," "support form," "contact us," "reach us," "contact information," "support contact," or "inquiry form." For sitewide page planning, use website-structure. metadata: version: 1.0.1
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
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
Other skills on kostja94-marketing-skills.
- /google-search-console
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries,"
Open skill - /seo-monitoring
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document,"
Open skill - /ai-traffic
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to
Open skill - /traffic
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel
Open skill - /tracking
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event
Open skill - /community-forum
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia,"
Open skill