When the user wants to create, optimize, or audit a services page. Also use when the user mentions "services page," "what we offer," "service offerings," "consulting services," "service page," "offerings page," "service catalog," or "professional services." For sitewide page planning, use website-structure.
Guides services page content and structure for service-based businesses (consulting, agencies, freelancers).
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 service offerings and differentiation.
Identify:
| Approach | When | |----------|------| | Single page | Few services; compact overview | | Hub + detail | Many services; main page links to each | | Service tiers | Packages, pricing tiers |
| Element | Purpose | |---------|---------| | Service overview | What you offer; who it's for | | Benefits | Outcomes, not just features | | Process | How you work; steps | | Proof | Case studies, testimonials | | CTA | Contact, get quote, book call |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/services · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/services"
cp -r "skills/pages/marketing/services" ".claude/skills/services"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.