product-marketing-context by coreyhaines31/marketingskills
npx skills add https://github.com/coreyhaines31/marketingskills --skill product-marketing-context你帮助用户创建和维护一份产品营销背景文档。这份文档记录了基础的定位和核心信息,供其他营销技能参考,从而避免用户重复工作。
文档存储在 .agents/product-marketing-context.md。
首先,检查 .agents/product-marketing-context.md 是否已存在。同时检查 .claude/product-marketing-context.md 以兼容旧版设置——如果在那里找到但不在 .agents/ 目录下,则询问是否要移动它。
如果文档已存在:
如果文档不存在,提供两个选项:
从代码库自动草拟(推荐):你将研究代码库——README、落地页、营销文案、package.json 等——并草拟一份 V1 版本的背景文档。然后由用户审查、更正并填补空白。这比从头开始要快。
从头开始:通过对话方式逐步引导用户完成每个部分,一次收集一个部分的信息。
大多数用户倾向于选择选项 1。在呈现草稿后,询问:"哪些地方需要更正?缺少什么内容?"
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
如果选择自动草拟:
如果选择从头开始: 通过对话方式逐步引导用户完成下面的每个部分,一次一个。不要一次性抛出所有问题。
对于每个部分:
力求获取客户的原话——确切的短语比经过润色的描述更有价值,因为它们反映了客户实际的想法和表达方式,这能使文案更具共鸣。
如果购买过程涉及多个利益相关者,为每个角色捕获:
JTBD 四力模型:
收集信息后,使用以下结构创建 .agents/product-marketing-context.md:
# Product Marketing Context
*Last updated: [date]*
## Product Overview
**One-liner:**
**What it does:**
**Product category:**
**Product type:**
**Business model:**
## Target Audience
**Target companies:**
**Decision-makers:**
**Primary use case:**
**Jobs to be done:**
-
**Use cases:**
-
## Personas
| Persona | Cares about | Challenge | Value we promise |
|---------|-------------|-----------|------------------|
| | | | |
## Problems & Pain Points
**Core problem:**
**Why alternatives fall short:**
-
**What it costs them:**
**Emotional tension:**
## Competitive Landscape
**Direct:** [Competitor] — falls short because...
**Secondary:** [Approach] — falls short because...
**Indirect:** [Alternative] — falls short because...
## Differentiation
**Key differentiators:**
-
**How we do it differently:**
**Why that's better:**
**Why customers choose us:**
## Objections
| Objection | Response |
|-----------|----------|
| | |
**Anti-persona:**
## Switching Dynamics
**Push:**
**Pull:**
**Habit:**
**Anxiety:**
## Customer Language
**How they describe the problem:**
- "[verbatim]"
**How they describe us:**
- "[verbatim]"
**Words to use:**
**Words to avoid:**
**Glossary:**
| Term | Meaning |
|------|---------|
| | |
## Brand Voice
**Tone:**
**Style:**
**Personality:**
## Proof Points
**Metrics:**
**Customers:**
**Testimonials:**
> "[quote]" — [who]
**Value themes:**
| Theme | Proof |
|-------|-------|
| | |
## Goals
**Business goal:**
**Conversion action:**
**Current metrics:**
.agents/product-marketing-context.md/product-marketing-context 来更新它。"每周安装量
27.4K
代码仓库
GitHub 星标数
15.9K
首次出现
2026 年 1 月 27 日
安全审计
安装于
opencode24.5K
codex24.3K
gemini-cli24.2K
github-copilot23.3K
kimi-cli22.5K
amp22.4K
You help users create and maintain a product marketing context document. This captures foundational positioning and messaging information that other marketing skills reference, so users don't repeat themselves.
The document is stored at .agents/product-marketing-context.md.
First, check if .agents/product-marketing-context.md already exists. Also check .claude/product-marketing-context.md for older setups — if found there but not in .agents/, offer to move it.
If it exists:
If it doesn't exist, offer two options:
Auto-draft from codebase (recommended): You'll study the repo—README, landing pages, marketing copy, package.json, etc.—and draft a V1 of the context document. The user then reviews, corrects, and fills gaps. This is faster than starting from scratch.
Start from scratch : Walk through each section conversationally, gathering info one section at a time.
Most users prefer option 1. After presenting the draft, ask: "What needs correcting? What's missing?"
If auto-drafting:
If starting from scratch: Walk through each section below conversationally, one at a time. Don't dump all questions at once.
For each section:
Push for verbatim customer language — exact phrases are more valuable than polished descriptions because they reflect how customers actually think and speak, which makes copy more resonant.
If multiple stakeholders are involved in buying, capture for each:
The JTBD Four Forces:
After gathering information, create .agents/product-marketing-context.md with this structure:
# Product Marketing Context
*Last updated: [date]*
## Product Overview
**One-liner:**
**What it does:**
**Product category:**
**Product type:**
**Business model:**
## Target Audience
**Target companies:**
**Decision-makers:**
**Primary use case:**
**Jobs to be done:**
-
**Use cases:**
-
## Personas
| Persona | Cares about | Challenge | Value we promise |
|---------|-------------|-----------|------------------|
| | | | |
## Problems & Pain Points
**Core problem:**
**Why alternatives fall short:**
-
**What it costs them:**
**Emotional tension:**
## Competitive Landscape
**Direct:** [Competitor] — falls short because...
**Secondary:** [Approach] — falls short because...
**Indirect:** [Alternative] — falls short because...
## Differentiation
**Key differentiators:**
-
**How we do it differently:**
**Why that's better:**
**Why customers choose us:**
## Objections
| Objection | Response |
|-----------|----------|
| | |
**Anti-persona:**
## Switching Dynamics
**Push:**
**Pull:**
**Habit:**
**Anxiety:**
## Customer Language
**How they describe the problem:**
- "[verbatim]"
**How they describe us:**
- "[verbatim]"
**Words to use:**
**Words to avoid:**
**Glossary:**
| Term | Meaning |
|------|---------|
| | |
## Brand Voice
**Tone:**
**Style:**
**Personality:**
## Proof Points
**Metrics:**
**Customers:**
**Testimonials:**
> "[quote]" — [who]
**Value themes:**
| Theme | Proof |
|-------|-------|
| | |
## Goals
**Business goal:**
**Conversion action:**
**Current metrics:**
.agents/product-marketing-context.md/product-marketing-context anytime to update it."Weekly Installs
27.4K
Repository
GitHub Stars
15.9K
First Seen
Jan 27, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode24.5K
codex24.3K
gemini-cli24.2K
github-copilot23.3K
kimi-cli22.5K
amp22.4K
48,100 周安装