use-cases-page-generator by kostja94/marketing-skills
npx skills add https://github.com/kostja94/marketing-skills --skill use-cases-page-generator指导撰写连接产品功能与真实客户问题的使用案例页面。场景优先是主要的组织原则。适用于 SaaS/B2B 的漏斗底部页面。回答"我何时会用到它?"和"它如何帮助我?"——区别于解决方案页面。
调用时机:在首次使用时,如果有助于理解,可以用 1-2 句话开头,说明此技能涵盖的内容及其重要性,然后提供主要输出。在后续使用或用戸要求跳过时,直接进入主要输出。
首先检查项目上下文: 如果存在 .claude/project-context.md 或 .cursor/project-context.md 文件,请读取其中的产品、理想客户画像和证明点信息。
识别:
| 部分 | 目的 |
|---|---|
| 标题 | "当您需要 X 时,我们帮助您 Y" 或 "面向 [角色]:解决 X" |
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 问题 | 痛点、日常挑战 |
| 解决方案 | 产品如何解决这些问题;链接到相关功能 |
| 证明 | 案例研究、客户评价、数据指标 |
| 行动号召 | 免费试用、预约演示、联系我们 |
| 相关 | 链接到其他使用案例、上级解决方案 |
| 维度 | 优先级 | 示例 |
|---|---|---|
| 按场景 | 主要 | 活动营销、潜在客户培育、防止流失、客户入门 |
| 按角色 | 主要 | 面向房地产经纪人、面向首席营销官、面向销售代表 |
| 按商业目标 | 次要 | 获客、留存、增销/交叉销售 |
| 按行业 | 次要 | 用作理想客户画像标签;或作为解决方案下的子页面 |
活动营销、潜在客户培育、防止流失、客户入门、患者预约、远程医疗、库存管理、需求预测。
获客、留存、增销/交叉销售。
| 页面类型 | 回答的问题 | 主要组织方式 |
|---|---|---|
| 功能 | 它能做什么? | 按能力 |
| 解决方案 | 我能获得什么结果? | 按行业、公司规模、团队 |
| 使用案例 | 我何时会用到它? | 按场景、角色、商业目标 |
层级关系:使用案例可以是独立的,也可以是解决方案下的子页面。例如:/solutions/healthcare/patient-scheduling。
| 需求 | 使用 |
|---|---|
| 按场景 | 使用案例 |
| 按角色 | 使用案例 |
| 按商业目标 | 使用案例 |
| 按行业 | 解决方案 |
| 按公司规模 | 解决方案 |
| 按团队 | 解决方案 |
| 行业特定应用 | 使用案例 |
每周安装量
201
代码仓库
GitHub 星标数
239
首次出现
Mar 1, 2026
安全审计
安装于
kimi-cli183
cursor183
gemini-cli182
codex182
github-copilot182
opencode182
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.
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:
| Section | Purpose |
|---|---|
| Headline | "When you need to X, we help you Y" or "For [role]: solve X" |
| Problem | Pain points, day-to-day challenges |
| Solution | How product addresses them; link to relevant features (do not duplicate feature copy) |
| Proof | Case study, testimonial, metrics |
| CTA | Try free, book demo, contact |
| Related | Link to other use cases, parent solution |
| Dimension | Priority | Examples |
|---|---|---|
| By Scenario | Primary | Event marketing, Lead nurturing, Churn prevention, Customer onboarding |
| By Persona/Role | Primary | For Realtors, For CMOs, For Sales Reps |
| By Business Goal | Secondary | Acquisition, Retention, Upsell/Cross-sell |
| By Industry | Secondary (ICP) | Use as ICP tag; or as sub-page under Solutions |
Event marketing, Lead nurturing, Churn prevention, Customer onboarding, Patient scheduling, Telemedicine, Inventory management, Demand forecasting.
Acquisition (signups, trials), Retention (reduce churn, re-engagement), Upsell/Cross-sell (expand revenue).
| Page | Answers | Primary Organization |
|---|---|---|
| Features | What does it do? | Capabilities |
| Solutions | What outcome do I get? | By industry, company size, team |
| Use cases | When would I use it? | By scenario, persona, business goal |
Hierarchy : Use cases can be standalone or sub-pages under Solutions. Example: /solutions/healthcare/patient-scheduling (use case under industry solution).
| Need | Use |
|---|---|
| By scenario (Event marketing) | Use Cases |
| By persona (For Realtors, For CMOs) | Use Cases |
| By business goal (Acquisition, Retention) | Use Cases |
| By industry | Solutions |
| By company size (SMB, Enterprise) | Solutions |
| By team (Marketing, Sales) | Solutions |
| Industry-specific application | Use Cases (as Solutions sub-page) |
Weekly Installs
201
Repository
GitHub Stars
239
First Seen
Mar 1, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
kimi-cli183
cursor183
gemini-cli182
codex182
github-copilot182
opencode182
社交媒体内容策略指南:创建、优化与互动全流程 | 营销技能
37,000 周安装