選項
首頁首頁 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:用於市場定位與上市策略。從此背景中解讀競爭格局。
  • 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 會自動偵測並使用該技能

相關技能

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