about-page-generator
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.
What this skill does
# 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
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".