/product-marketing-context
プロダクトマーケティングのコンテキスト文書を作成・更新するスキル。 「マーケティングコンテキストを作成」「ポジショニングを整理」「製品情報をまとめて」等のリクエストで発動。
$ npx -y skills add minicoohei/ai-agent-camp --skill product-marketing-context --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/product-marketing-context
Context preview
The summary Claude sees to decide when to auto-load this skill.
プロダクトマーケティングのコンテキスト文書を作成・更新するスキル。 「マーケティングコンテキストを作成」「ポジショニングを整理」「製品情報をまとめて」等のリクエストで発動。
SKILL.md
product-marketing-context.SKILL.mdname: product-marketing-context
version: 1.0.0
description: "プロダクトマーケティングのコンテキスト文書を作成・更新するスキル。 「マーケティングコンテキストを作成」「ポジショニングを整理」「製品情報をまとめて」等のリクエストで発動。"
triggers:
- マーケティングコンテキストを作成
- ポジショニングを整理
- 製品情報をまとめて
- プロダクトコンテキスト
- ターゲット顧客を定義
- product-marketing-context
- product context
Product Marketing Context
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 `.claude/product-marketing-context.md`.
Workflow
Step 1: Check for Existing Context
First, check if `.claude/product-marketing-context.md` already exists.
**If it exists:**
- Read it and summarize what's captured
- Ask which sections they want to update
- Only gather info for those sections
**If it doesn't exist, offer two options:**
1. **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.
2. **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?"
Step 2: Gather Information
**If auto-drafting:** 1. Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs 2. Draft all sections based on what you find 3. Present the draft and ask what needs correcting or is missing 4. Iterate until the user is satisfied
**If starting from scratch:** Walk through each section below conversationally, one at a time. Don't dump all questions at once.
For each section: 1. Briefly explain what you're capturing 2. Ask relevant questions 3. Confirm accuracy 4. Move to the next
**Important:** Push for verbatim customer language. Exact phrases are more valuable than polished descriptions.
---
Sections to Capture
1. Product Overview
- One-line description
- What it does (2-3 sentences)
- Product category (what "shelf" you sit on—how customers search for you)
- Product type (SaaS, marketplace, e-commerce, service, etc.)
- 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 (B2B only)
If multiple stakeholders are involved in buying, capture for each:
- User, Champion, Decision Maker, Financial Buyer, Technical Influencer
- What each cares about, their challenge, and 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 (e.g., Calendly vs SavvyCal)
- **Secondary competitors**: Different solution, same problem (e.g., Calendly vs Superhuman scheduling)
- **Indirect competitors**: Conflicting approach (e.g., Calendly vs personal assistant)
- How each falls short for customers
6. Differentiation
- Key differentiators (capabilities alternatives lack)
- How you solve it differently
- Why that's better (benefits)
- Why customers choose you over alternatives
7. Objections & Anti-Personas
- Top 3 objections heard in sales and how to address them
- Who is NOT a good fit (anti-persona)
8. Switching Dynamics
The JTBD Four Forces:
- **Push**: What frustrations drive 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
- How customers describe the problem (verbatim)
- How they describe your solution (verbatim)
- Words/phrases to use
- Words/phrases to avoid
- Glossary of product-specific terms
10. Brand Voice
- Tone (professional, casual, playful, etc.)
- Communication style (direct, conversational, technical)
- Brand personality (3-5 adjectives)
11. Proof Points
- Key metrics or results to cite
- Notable customers/logos
- Testimonial snippets
- Main value themes and supporting evidence
12. Goals
- Primary business goal
- Key conversion action (what you want people to do)
- Current metrics (if known)
---
Step 3: Create the Document
After gathering information, create `.claude/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 |
|------|---------|
| | |
## Bra
Read more
name: product-marketing-context version: 1.0.0 description: "プロダクトマーケティングのコンテキスト文書を作成・更新するスキル。 「マーケティングコンテキストを作成」「ポジショニングを整理」「製品情報をまとめて」等のリクエストで発動。" triggers: - マーケティングコンテキストを作成 - ポジショニングを整理 - 製品情報をまとめて - プロダクトコンテキスト - ターゲット顧客を定義 - product-marketing-context - product context
Product Marketing Context
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 `.claude/product-marketing-context.md`.
Workflow
Step 1: Check for Existing Context
First, check if `.claude/product-marketing-context.md` already exists.
**If it exists:**
- Read it and summarize what's captured
- Ask which sections they want to update
- Only gather info for those sections
**If it doesn't exist, offer two options:**
1. **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.
2. **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?"
Step 2: Gather Information
**If auto-drafting:** 1. Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs 2. Draft all sections based on what you find 3. Present the draft and ask what needs correcting or is missing 4. Iterate until the user is satisfied
**If starting from scratch:** Walk through each section below conversationally, one at a time. Don't dump all questions at once.
For each section: 1. Briefly explain what you're capturing 2. Ask relevant questions 3. Confirm accuracy 4. Move to the next
**Important:** Push for verbatim customer language. Exact phrases are more valuable than polished descriptions.
---
Sections to Capture
1. Product Overview
- One-line description
- What it does (2-3 sentences)
- Product category (what "shelf" you sit on—how customers search for you)
- Product type (SaaS, marketplace, e-commerce, service, etc.)
- 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 (B2B only)
If multiple stakeholders are involved in buying, capture for each:
- User, Champion, Decision Maker, Financial Buyer, Technical Influencer
- What each cares about, their challenge, and 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 (e.g., Calendly vs SavvyCal)
- **Secondary competitors**: Different solution, same problem (e.g., Calendly vs Superhuman scheduling)
- **Indirect competitors**: Conflicting approach (e.g., Calendly vs personal assistant)
- How each falls short for customers
6. Differentiation
- Key differentiators (capabilities alternatives lack)
- How you solve it differently
- Why that's better (benefits)
- Why customers choose you over alternatives
7. Objections & Anti-Personas
- Top 3 objections heard in sales and how to address them
- Who is NOT a good fit (anti-persona)
8. Switching Dynamics
The JTBD Four Forces:
- **Push**: What frustrations drive 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
- How customers describe the problem (verbatim)
- How they describe your solution (verbatim)
- Words/phrases to use
- Words/phrases to avoid
- Glossary of product-specific terms
10. Brand Voice
- Tone (professional, casual, playful, etc.)
- Communication style (direct, conversational, technical)
- Brand personality (3-5 adjectives)
11. Proof Points
- Key metrics or results to cite
- Notable customers/logos
- Testimonial snippets
- Main value themes and supporting evidence
12. Goals
- Primary business goal
- Key conversion action (what you want people to do)
- Current metrics (if known)
---
Step 3: Create the Document
After gathering information, create `.claude/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 | |------|---------| | | | ## Bra
AI Agent Training for Non-Engineers - Complete Guide to Claude Code / Cursor / Codex ### ⚠️ Before you clone Official repository (maintained by the authors): Running AI agents from this repo grants them shell, file-write, and external-API permissions on your
Other skills on ai-agent-camp.
- /ab-test-setup
A/Bテストや実験の設計・実装を支援するスキル。 「A/Bテストを設計して」「スプリットテストしたい」「仮説を立ててテストしたい」「バリアントを比較」等のリクエストで発動。 トラッキング実装は analytics-tracking を参照。
Open skill - /agent-designer
マルチエージェントシステムのアーキテクチャ設計ツールキット。 「エージェントを設計して」「マルチエージェント構成」「エージェントのアーキテクチャ」「オーケストレーション設計」等のリクエストで発動。
Open skill - /analytics-tracking
アナリティクスのトラッキング設定・改善・監査を支援するスキル。 「トラッキングを設定」「GA4を導入」「コンバージョン計測」「イベントトラッキング」「UTMパラメータ」「GTMの設定」等のリクエストで発動。 A/Bテスト計測は ab-test-setup を参照。
Open skill - /article-writer
テーマからアウトライン生成→文体プロファイル適用→Markdown記事出力を行う記事執筆スキル。 挿絵マーカーの自動挿入、style-analyzerプロファイル参照による文体統一に対応。 「記事を書いて」「ブログ作成」「テーマで記事生成」等のリクエストで発動。
Open skill - /banner-creator
各種SNS・広告プラットフォーム向けのバナー/クリエイティブを生成するスキル。 X, Facebook, Instagram, PRTimes, YouTube, LINE, Web広告に対応。 「バナーを作って」「広告画像を生成」「SNS用の画像」「クリエイティブ制作」等のリクエストで発動。
Open skill - /bigquery-auth
GCPプロジェクト単位でBigQuery認証を設定するスキル。 gcloud設定プロファイルで複数プロジェクトを安全に分離管理。 「BigQueryに繋ぎたい」「BQ認証」「gcloud認証」「データ分析の認証設定」等のリクエストで発動。
Open skill

