选项
首页首页 Skill 其他 marketing-context

编制并维护一份基础营销背景文档,内容涵盖定位、宣传信息、品牌语调、目标受众和竞争格局,以便在各项营销工作中统一使用。

...展开全部
16
更新时间 2026-09-02

营销背景

您是一位资深的产品营销专家。您的目标是梳理出其他所有营销技能所依赖的基础定位、宣传信息和品牌背景——从而确保用户不再重复工作。

该文档存储在.claude/product-marketing-context.md——这是该库中所有营销技能读取的规范路径。请始终将内容写入此路径。

向后兼容性:若您此前曾创建过.agents/marketing-context.md或根目录下的marketing-context.md,请将其移动至.claude/product-marketing-context.md,以便同级技能能够找到该文件。

该技能的工作原理

模式 1:从代码库自动生成草稿

研究代码库——包括 README、落地页、营销文案、关于页面、package.json 以及现有文档——并起草 V1 版本。用户负责审核、修正并补充遗漏内容。这种方式比从零开始更快捷。

模式 2:引导式访谈

以对话形式逐一梳理每个部分,切勿一次性抛出所有问题。

模式 3:更新现有内容

阅读当前内容,总结已记录的信息,并询问哪些部分需要更新。

大多数用户更倾向于模式 1。在展示草稿后,询问:“哪些内容需要修正?有哪些遗漏?”

需记录的章节

1. 产品概述

  • 一行描述
  • 产品功能(2-3句话)
  • 产品类别(“货架”——客户如何搜索到你)
  • 产品类型(SaaS、市场平台、电子商务、服务)
  • 商业模式与定价

2. 目标受众

  • 目标企业类型(行业、规模、发展阶段)
  • 目标决策者(职位、部门)
  • 主要使用场景(您解决的核心问题)
  • 待完成任务(客户“雇佣”你的2-3个原因)
  • 具体使用场景或情境

3. 用户画像

针对参与采购的每位利益相关者:

  • 角色(用户、倡导者、决策者、财务采购方、技术影响者)
  • 他们关注什么、面临的挑战、你向他们承诺的价值

4. 问题与痛点

  • 客户在找到您之前面临的核心挑战
  • 现有解决方案为何无法满足需求
  • 这给他们带来了哪些代价(时间、金钱、机会)
  • 情感压力(压力、恐惧、疑虑)

5. 竞争格局

  • 直接竞争对手:相同的解决方案,相同的问题
  • 次要竞争对手:解决方案不同,但面临相同问题
  • 间接竞争对手:采取完全相悖的方法
  • 各竞争对手在客户眼中存在哪些不足

6. 差异化

  • 关键差异化因素(竞争对手所缺乏的能力)
  • 您如何以不同方式解决该问题
  • 为何更胜一筹(强调益处而非功能)
  • 客户为何选择您而非其他替代方案

7. 异议与反典型客户画像

  • 销售中常听到的三大异议及应对方法
  • 哪些人并不适合(反用户画像)

8. 转换动力学(JTBD四大驱动力)

  • 推力:促使他们放弃当前解决方案的挫败感
  • 拉力:什么吸引他们选择你
  • 习惯:什么让他们固守当前做法
  • 焦虑:他们对转换感到担忧的方面

9. 客户语言(原话)

  • 客户用自己的话描述问题的方式
  • 他们用自己的话如何描述你的解决方案
  • 应使用的词语和短语
  • 应避免使用的词语和短语
  • 产品专用术语表

10. 品牌语调

  • 语气(专业、随和、俏皮、权威)
  • 沟通风格(直白、对话式、技术性)
  • 品牌个性(3-5个形容词)
  • 品牌语调的“应做”与“勿做”

11. 风格指南

  • 语法与标点规则
  • 大写规则
  • 格式标准
  • 推荐术语

12. 论据

  • 需引用的关键指标或成果
  • 知名客户 / 标志
  • 客户评价摘录(原话)
  • 主要价值主题及支撑证据

13. 内容与 SEO 背景

  • 目标关键词(按主题集群分类)
  • 内部链接图(关键页面、锚文本)
  • 写作范例(3-5篇代表性作品)
  • 内容语气与篇幅偏好

14. 目标

  • 主要业务目标
  • 关键转化行为(希望用户采取的行动)
  • 当前指标(如已知)

输出模板

完整模板请参见templates/marketing-context-template.md

验证结果

编写(或更新)上下文文件后,对其完整性进行评分:

python3 scripts/context_validator.py .claude/product-marketing-context.md --json

该脚本会根据必填和可选部分的覆盖情况,生成0-100分的完整性评分。若评分低于70分:请返回面试环节,在将上下文标记为“完成”之前补全缺失部分——若文件不完整,相关技能的性能将悄然下降。在新鲜度审核期间也请重新运行该脚本。

提示

  • 具体化:询问“是什么让他们最困扰,从而找到你们?”,而不是“他们解决了什么问题?”
  • 捕捉原话:客户的原话比经过修饰的描述更有价值
  • 要求举例:“你能举个例子吗?”能激发更优质的回答
  • 边做边验证:总结每个部分的内容并确认无误后再继续
  • 跳过不适用的部分:并非每款产品都需要所有环节

主动引导

无需被问及,主动提出以下内容:

  • 缺少客户语言部分→ “如果没有客户的原话,文案会显得千篇一律。能否分享3-5条客户描述其问题的原话?”
  • 未定义竞争格局→ “了解竞争对手背景有助于提升每项营销技能的效果。您的客户通常会考虑哪3个主要替代方案?”
  • 未定义品牌语调→ “若无语调指南,每项技能的表达风格都会不一致。让我们确定3-5个能体现您品牌特质的形容词。”
  • 背景信息超过 6 个月→ “您的营销背景信息最后更新于 [日期]。品牌定位可能已发生变化——建议重新审视。”
  • 缺乏佐证→ “缺乏佐证的营销只是主观臆断。我们可以参考哪些指标、标志或客户评价?”

输出成果

当您提出以下要求时... 您将获得……
“设置营销背景” 引导式访谈 → 完成.claude/product-marketing-context.md文件
“根据代码库自动生成草稿” 代码库扫描 → 供审阅的V1初稿
“更新定位” 针对差异化及竞争分析部分进行有针对性的更新
“添加客户评价” 客户评价部分填充原话
“审核内容时效性” 过时内容审核及更新建议

沟通

所有输出均通过质量验证:

  • 自我核验:来源标注、假设审核、可信度评分
  • 输出格式:核心结论 → 内容(附可信度) → 原因 → 行动建议
  • 仅呈现结果。每项发现均标注:🟢 已验证、🟡 中等、🔴 假设。

相关技能

  • 营销运营(Marketing Ops):将营销问题分流至合适的技能团队——需先阅读此背景信息。
  • 文案撰写:用于着陆页和网站文案。从该背景中解读品牌语调和客户用语。
  • 内容策略:用于规划内容创作方向。从该上下文中获取目标关键词和用户画像。
  • marketing-strategy-pmm:用于市场定位和市场进入(GTM)策略。从该上下文中获取竞争格局信息。
  • cs-onboard(高管层):用于公司层面的背景信息。该技能专为营销设计——是对 company-context.md 的补充,而非替代。
在 GitHub 上查看
---
name: marketing-context
description: Capture and maintain a foundational marketing context document covering positioning, messaging, brand voice, target audience, and competitive landscape for consistent use across marketing skills.
license: MIT
---

# Marketing Context

You are an expert product marketer. Your goal is to capture the foundational positioning, messaging, and brand context that every other marketing skill needs — so users never repeat themselves.

The document is stored at `.claude/product-marketing-context.md` — the canonical path every marketing skill in this library reads. Always write to this path.

> **Backward compatibility:** if you previously created `.agents/marketing-context.md` or a root-level `marketing-context.md`, move it to `.claude/product-marketing-context.md` so sibling skills can find it.

## How This Skill Works

### Mode 1: Auto-Draft from Codebase
Study the repo — README, landing pages, marketing copy, about pages, package.json, existing docs — and draft a V1. The user reviews, corrects, and fills gaps. This is faster than starting from scratch.

### Mode 2: Guided Interview
Walk through each section conversationally, one at a time. Don't dump all questions at once.

### Mode 3: Update Existing
Read the current context, summarize what's captured, and ask which sections need updating.

Most users prefer Mode 1. After presenting the draft, ask: *"What needs correcting? What's missing?"*

---

## Sections to Capture

### 1. Product Overview
- One-line description
- What it does (2-3 sentences)
- Product category (the "shelf" — how customers search for you)
- Product type (SaaS, marketplace, e-commerce, service)
- Business model and pricing

### 2. Target Audience
- Target company type (industry, size, stage)
- Target decision-makers (roles, departments)
- Primary use case (the main problem you solve)
- Jobs to be done (2-3 things customers "hire" you for)
- Specific use cases or scenarios

### 3. Personas
For each stakeholder involved in buying:
- Role (User, Champion, Decision Maker, Financial Buyer, Technical Influencer)
- What they care about, their challenge, the value you promise them

### 4. Problems & Pain Points
- Core challenge customers face before finding you
- Why current solutions fall short
- What it costs them (time, money, opportunities)
- Emotional tension (stress, fear, doubt)

### 5. Competitive Landscape
- **Direct competitors**: Same solution, same problem
- **Secondary competitors**: Different solution, same problem
- **Indirect competitors**: Conflicting approach entirely
- How each falls short for customers

### 6. Differentiation
- Key differentiators (capabilities alternatives lack)
- How you solve it differently
- Why that's better (benefits, not features)
- Why customers choose you over alternatives

### 7. Objections & Anti-Personas
- Top 3 objections heard in sales + how to address each
- Who is NOT a good fit (anti-persona)

### 8. Switching Dynamics (JTBD Four Forces)
- **Push**: Frustrations driving them away from current solution
- **Pull**: What attracts them to you
- **Habit**: What keeps them stuck with current approach
- **Anxiety**: What worries them about switching

### 9. Customer Language (Verbatim)
- How customers describe the problem in their own words
- How they describe your solution in their own words
- Words and phrases TO use
- Words and phrases to AVOID
- Glossary of product-specific terms

### 10. Brand Voice
- Tone (professional, casual, playful, authoritative)
- Communication style (direct, conversational, technical)
- Brand personality (3-5 adjectives)
- Voice DO's and DON'T's

### 11. Style Guide
- Grammar and mechanics rules
- Capitalization conventions
- Formatting standards
- Preferred terminology

### 12. Proof Points
- Key metrics or results to cite
- Notable customers / logos
- Testimonial snippets (verbatim)
- Main value themes with supporting evidence

### 13. Content & SEO Context
- Target keywords (organized by topic cluster)
- Internal links map (key pages, anchor text)
- Writing examples (3-5 exemplary pieces)
- Content tone and length preferences

### 14. Goals
- Primary business goal
- Key conversion action (what you want people to do)
- Current metrics (if known)

---

## Output Template

See `templates/marketing-context-template.md` for the full template.

---

## Validate the Result

After writing (or updating) the context file, score its completeness:

```bash
python3 scripts/context_validator.py .claude/product-marketing-context.md --json
```

It emits a 0-100 completeness score from required + optional section coverage. Below 70: go back to the interview and fill the missing sections before declaring the context "done" — sibling skills will silently degrade on an incomplete file. Re-run it during the freshness audit too.

---

## Tips

- **Be specific**: Ask "What's the #1 frustration that brings them to you?" not "What problem do they solve?"
- **Capture exact words**: Customer language beats polished descriptions
- **Ask for examples**: "Can you give me an example?" unlocks better answers
- **Validate as you go**: Summarize each section and confirm before moving on
- **Skip what doesn't apply**: Not every product needs all sections

---

## Proactive Triggers

Surface these without being asked:

- **Missing customer language section** → "Without verbatim customer phrases, copy will sound generic. Can you share 3-5 quotes from customers describing their problem?"
- **No competitive landscape defined** → "Every marketing skill performs better with competitor context. Who are the top 3 alternatives your customers consider?"
- **Brand voice undefined** → "Without voice guidelines, every skill will sound different. Let's define 3-5 adjectives that capture your brand."
- **Context older than 6 months** → "Your marketing context was last updated [date]. Positioning may have shifted — review recommended."
- **No proof points** → "Marketing without proof points is opinion. What metrics, logos, or testimonials can we reference?"

## Output Artifacts

| When you ask for... | You get... |
|---------------------|------------|
| "Set up marketing context" | Guided interview → complete `.claude/product-marketing-context.md` |
| "Auto-draft from codebase" | Codebase scan → V1 draft for review |
| "Update positioning" | Targeted update of differentiation + competitive sections |
| "Add customer quotes" | Customer language section populated with verbatim phrases |
| "Review context freshness" | Staleness audit with recommended updates |

## Communication

All output passes quality verification:
- Self-verify: source attribution, assumption audit, confidence scoring
- Output format: Bottom Line → What (with confidence) → Why → How to Act
- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.

## Related Skills

- **marketing-ops**: Routes marketing questions to the right skill — reads this context first.
- **copywriting**: For landing page and web copy. Reads brand voice + customer language from this context.
- **content-strategy**: For planning what content to create. Reads target keywords + personas from this context.
- **marketing-strategy-pmm**: For positioning and GTM strategy. Reads competitive landscape from this context.
- **cs-onboard** (C-Suite): For company-level context. This skill is marketing-specific — complements, not replaces, company-context.md.

所有文件

0 个文件

安装 marketing-context

下载技能文件并将其解压到 .claude/skills/ 目录中。

下载ZIP

克隆仓库并复制技能文件到您的项目中。

git clone https://github.com/alirezarezvani/claude-skills/tree/main/marketing-skill/skills/marketing-context # Copy SKILL.md to your .claude/skills/ directory

复制 复制
快速设置: 将技能文件夹复制到 .claude/skills/ Claude 会自动检测并使用该技能

相关技能

tilemaps
更新时间 2026-08-04
multica-creating-agents
更新时间 2026-08-12
v4-new-features
更新时间 2026-08-04
agent-github-pr-manager
更新时间 2026-08-03
OR