about-page-generator
The about-page-generator skill guides creation and optimization of About page content for company websites, covering structure, messaging, team presentation, and trust-building elements. Use it when users request About page creation, want to improve existing About content, audit page effectiveness, or mention related terms like "company story," "team page," or "who we are." The skill provides assessment frameworks, best practices for storytelling and customer focus, schema markup guidance, and output templates for structure, narrative, SEO metadata, and trust elements.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/about-page-generator && cp -r /tmp/about-page-generator/skills/pages/brand/about ~/.claude/skills/about-page-generatorSKILL.md
# Pages: About Guides About page content, structure, and trust-building for company websites. **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 company story, values, and differentiation. See **branding** for full brand strategy framework (purpose, values, storytelling). Identify: 1. **Audience**: Job seekers, buyers, partners, press 2. **Key message**: Mission, values, differentiation 3. **Proof points**: Awards, metrics, testimonials ## Best Practices ### Essential Elements | Element | Purpose | |---------|---------| | **Company overview** | Who, what, where, when, why, how | | **Origin story** | Journey, founding, milestones | | **Team** | Key people, photos, roles | | **Mission and values** | What you stand for | | **Visuals** | Photos, videos, office/culture | | **Social proof** | Testimonials, awards, certifications | | **Contact** | Easy way to reach you | ### Strategic Approach - **Tell a story**: Convey who you are and why you're different—not just facts. See **branding** for origin story, hero's journey, narrative arc. - **Customer-focused**: Frame around what you solve for customers, not self-promotion - **Build trust**: Social links, testimonials, contact details, certifications - **Visible placement**: About in main nav, not buried in footer ### Schema (AboutPage, Not Organization) - **AboutPage** schema: Use on About page—describes page content (headline, description, author, about). Helps search engines understand this page's purpose. - **Organization** schema: Place on **homepage or root layout**, not About. Organization is entity-level (brand that owns the site); AboutPage is page-level. See **schema-markup** for placement. ### Why It Matters - One of the most-visited pages - 58% of customers buy based on company values - 60% of job candidates choose employers based on values - Entry point for branded search; impacts conversions ## Output Format - **Structure** outline (sections) - **Story** narrative and key messages - **Team** section approach - **SEO** metadata (title, description, H1) - **Trust** elements checklist ## Related Skills - **branding**: Brand strategy, storytelling, purpose, values; About page implements brand story - **homepage-generator**: About often linked from homepage - **contact-page-generator**: Contact info on About - **customer-stories-page-generator**: Social proof complements About - **title-tag, meta-description, page-metadata**: About page metadata - **schema-markup**: AboutPage schema for About; Organization goes on homepage/root layout - **brand-protection**: Official domain and identity declaration; helps users distinguish from impersonation sites
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," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
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," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
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 track AI traffic." For AI SEO strategy, use generative-engine-optimization.
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 analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-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 setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
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," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.