skillboardUpdated every 6 hours
skillboardWhen 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.
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.
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:
| 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 |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/about · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/about"
cp -r "skills/pages/brand/about" ".claude/skills/about"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.