about-page-generator

$npx mdskill add kostja94/marketing-skills/about-page-generator

Generate, optimize, or audit About page content for company websites.

  • Creates or improves About pages for company story, team, and trust.
  • Reads project context files for company story, values, and differentiation.
  • Identifies audience, key message, and proof points from user input.
  • Outputs structured content with essential elements like origin story and social proof.

SKILL.md

.github/skills/about-page-generatorView on GitHub ↗
---
name: about-page-generator
description: When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
metadata:
  version: 1.0.1
---

# 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

More from kostja94/marketing-skills

SkillDescription
404-page-generatorWhen the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
affiliate-marketingWhen the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
affiliate-page-generatorWhen the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
ai-traffic-trackingWhen 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.
alternatives-page-generatorWhen the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
api-page-generatorWhen the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
app-adsWhen the user wants to run app install ads, user acquisition (UA), or promote mobile apps. Also use when the user mentions "app ads," "app install ads," "UA," "user acquisition," "Google App Campaigns," "Apple Search Ads," "ASA," "UAC," "App Store ads," "Play Store ads," "CPI," or "app promotion." For store listings, use distribution-channels.
article-contentWhen the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.
backlink-analysisWhen the user wants to analyze backlinks, audit link profile, or identify link issues. Also use when the user mentions "backlink analysis," "backlink audit," "referring domains," "toxic links," "link profile," or "disavow file." For acquisition, use link-building.
blog-page-generatorWhen the user wants to create, optimize, or audit blog index or listing page structure (not a single post). Also use when the user mentions "blog page," "blog index," "blog layout," "content hub," "blog homepage," "blog listing," "subdomain vs subdirectory," "blog structure," or "blog SEO." For single post page SEO and schema, use article-page-generator.