use-cases-page-generator
When the user wants to create, optimize, or audit use case pages. Also use when the user mentions "use cases," "use case page," "for [role]," "by persona," "by scenario," "by business goal," "ICP pages," or "audience-specific pages." For sitewide page planning, use website-structure.
npx skills add kostja94/marketing-skills --skill use-cases --agent cursor
Same command for any agent — swap --agent for claude-code, codex, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Pages: Use Cases Guides use case pages that bridge product features and real-world customer problems. **Scenario-first** is the primary organization. BOFU (bottom-of-funnel) pages for SaaS/B2B. Answer "when would I use it?" and "how does it help me?" — distinct from solutions (industry/outcome). **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 product, ICP, and proof points. Identify: 1. **Scenarios**: Concrete situations (event marketing, lead nurturing) 2. **Personas**: Roles (Marketer, Sales Rep, Realtor) 3. **Business goals**: Acquisition, Retention, Upsell 4. **Format**: Single page vs. per-use-case pages; standalone or under solutions 5. **Primary goal**: Demo, sign up, contact sales ## Use Case Page Structure | Section | Purpose | |---------|---------| | **Headline** | "When you need to X, we help you Y" or "For [role]: solve X" | | **Problem** | Pain
- Initial Assessment
- Use Case Page Structure
- Best Practices
- Scenario-First
- Content Differentiation (vs Features)
- Organization (Primary → Secondary)
- Scenario Examples
- Business Goal Examples
- vs. Solutions vs. Features
- When to Use Use Cases vs Solutions
- Internal Linking
- SEO
- Output Format
- Related Skills
What does the use-cases-page-generator skill do?
When the user wants to create, optimize, or audit use case pages. Also use when the user mentions "use cases," "use case page," "for [role]," "by persona," "by scenario," "by business goal," "ICP pages," or "audience-specific pages." For sitewide page planning, use website-structure.
How do I install it?
Run `npx skills add kostja94/marketing-skills --skill use-cases --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From kostja94/marketing-skills, a repository with 848 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.