mcpbeat Sign in

About Page Generator Agent Skill

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.

839 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
836
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/kostja94/marketing-skills --skill about-page-generator

The instruction itself

9 sections, as written by the author

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:

  • Audience: Job seekers, buyers, partners, press
  • Key message: Mission, values, differentiation
  • 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
  • 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

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

4k tokens
File Organizer
by frostant
×10

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

3k tokens
Domain Name Brainstormer
by frostant
×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

1k tokens
Brainstorming
by ZhanlinCui
×4

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

626 tokens
Planning With Files
by ZhanlinCui
×3

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts
Scientific Brainstorming
by christophacham
×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens
GitHub Project Management
by ComeOnOliver
×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

14k tokens
Grill Me
by ComeOnOliver
×3

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens

How to use it

Copy the folder

Take kostja94/about-page-generator from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.