skillboardUpdated every 6 hours
skillboardWhen the user wants to create, optimize, or audit solutions pages. Also use when the user mentions "solutions," "solutions page," "by industry," "industry solutions," "by company size," "SMB," "enterprise," "by outcome," "business outcomes," or "how we solve X." For sitewide page planning, use website-structure.
Guides solutions pages focused on business outcomes. Industry-first is the B2B norm (Salesforce, HubSpot). Answer "what outcome do I get for my industry/team/size?" rather than "what does it do?" Distinct from features (capabilities) and use cases (scenarios); solutions emphasize measurable value by segment.
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 product, outcomes, and proof points.
Identify:
| Section | Purpose | |---------|---------| | Headline | Outcome-led; "Achieve X with [Product]" | | Challenge | Business problem, context | | Solution | How product delivers the outcome | | Proof | Metrics, case study, ROI | | Features used | Link to relevant features | | CTA | Book demo, start trial, see case study | | Related | Other solutions, use cases (as sub-applications) |
| Dimension | Priority | Examples | |-----------|----------|----------| | By Industry | Primary | Healthcare, Retail, Manufacturing, Financial Services | | By Company Size | Secondary | SMB, Mid-Market, Enterprise | | By Team | Secondary | Marketing, Sales, Service, Operations | | By Outcome | Alternative | Scale support, Reduce churn, Accelerate sales |
Automotive, Communications, Consumer Goods, Consumer Services, Construction & Real Estate, Education, Energy & Utilities, Financial Services, Government, Healthcare & Life Sciences, Manufacturing, Media, Nonprofit, Professional Services, Retail, Technology, Travel & Hospitality.
| Size | Typical | Focus | |------|---------|-------| | Startup | <50 | Speed, agility | | SMB | 50–500 | Ease of use, affordability | | Mid-Market | 500–5000 | Scalability | | Enterprise | 5000+ | Customization, compliance, integration |
| Page | Answers | Primary Organization | |------|---------|----------------------| | Features | What does it do? | Capabilities | | Use cases | When would I use it? | By scenario, persona, business goal | | Solutions | What outcome do I get? | By industry, company size, team |
Hierarchy: Solutions (industry/segment) can contain Use Cases as sub-applications. Example: /solutions/healthcare → use cases: patient scheduling, telemedicine.
| Need | Use | |------|-----| | By industry (Healthcare, Retail) | Solutions | | By company size (SMB, Enterprise) | Solutions | | By team (Marketing, Sales) | Solutions | | By outcome (Scale support) | Solutions | | By scenario (Event marketing) | Use Cases | | By persona (For Realtors, For CMOs) | Use Cases | | By business goal (Acquisition, Retention) | Use Cases | | Industry-specific application | Use Cases (as Solutions sub-page) |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/solutions · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/solutions"
cp -r "skills/pages/marketing/solutions" ".claude/skills/solutions"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.