Agent Skills
› sediman-agent/OpenSkynet
› contact-page-generator
contact-page-generator
GitHub用于创建、优化或审核联系页面及表单的助手。提供表单设计最佳实践，包括字段精简、单列布局、清晰标签和醒目CTA。同时涵盖页面布局、信任信号建立、SEO元数据及无障碍检查，以提升转化率和用户体验。
Trigger Scenarios
用户想要创建或优化联系页面
用户提到contact page, contact form, get in touch等关键词
需要审核联系表单的设计与文案
Install
npx skills add sediman-agent/OpenSkynet --skill contact-page-generator -g -y
SKILL.md
Frontmatter
{
"name": "contact-page-generator",
"metadata": {
"version": "1.0.1"
},
"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."
}
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:
- Contact types: Sales, support, general, press
- Form purpose: Lead capture, support ticket, demo request
- 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
Version History
- c9d8953 Current 2026-07-05 19:57
