product-marketing

Name: product-marketing
Author: coreyhaines31

39kinstalls6.5kforks

How to install product-marketing?

coreyhaines31/marketingskills/product-marketing

$npx -y skills add coreyhaines31/marketingskills --skill product-marketing

Installs into the current project.

Summary

When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants

Files · 1

View on GitHub

SKILL.md

1	# Product Marketing Context
2
3	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.
4
5	The document is stored at `.agents/product-marketing.md`.
6
7	## Workflow
8
9	### Step 1: Check for Existing Context
10
11	First, check if `.agents/product-marketing.md` already exists. Also check `.claude/product-marketing.md` and the legacy filename `product-marketing-context.md` (in either `.agents/` or `.claude/`) for older setups — if found anywhere other than `.agents/product-marketing.md`, offer to move it to the canonical location.
12
13	If it exists:
14	- Read it and summarize what's captured — note its current Document version and the last few Changelog entries so the user sees where the doc stands and what's changed recently
15	- Ask which sections they want to update
16	- Only gather info for those sections
17	- On any substantive save, bump the version and add a changelog entry (see Step 4). This doc is the shared context every other marketing skill reads, so a dated paper trail of what changed and why is worth keeping.
18
19	If it doesn't exist, offer two options:
20
21	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.
22
23	2. Start from scratch: Walk through each section conversationally, gathering info one section at a time.
24
25	Most users prefer option 1. After presenting the draft, ask: "What needs correcting? What's missing?"
26
27	### Step 2: Gather Information
28
29	If auto-drafting:
30	1. Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs
31	2. Draft all sections based on what you find
32	3. Present the draft and ask what needs correcting or is missing
33	4. Iterate until the user is satisfied
34
35	If starting from scratch:
36	Walk through each section below conversationally, one at a time. Don't dump all questions at once.
37
38	For each section:
39	1. Briefly explain what you're capturing
40	2. Ask relevant questions
41	3. Confirm accuracy
42	4. Move to the next
43
44	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.
45
46	---
47
48	## Sections to Capture
49
50	### 1. Product Overview
51	- One-line description
52	- What it does (2-3 sentences)
53	- Product category (what "shelf" you sit on—how customers search for you)
54	- Product type (SaaS, marketplace, e-commerce, service, etc.)
55	- Business model and pricing
56
57	### 2. Target Audience
58	- Target company type (industry, size, stage)
59	- Target decision-makers (roles, departments)
60	- Primary use case (the main problem you solve)
61	- Jobs to be done (2-3 things customers "hire" you for)
62	- Specific use cases or scenarios
63
64	### 3. Personas (B2B only)
65	If multiple stakeholders are involved in buying, capture for each:
66	- User, Champion, Decision Maker, Financial Buyer, Technical Influencer
67	- What each cares about, their challenge, and the value you promise them
68
69	### 4. Problems & Pain Points
70	- Core challenge customers face before finding you
71	- Why current solutions fall short
72	- What it costs them (time, money, opportunities)
73	- Emotional tension (stress, fear, doubt)
74
75	### 5. Competitive Landscape
76	- Direct competitors: Same solution, same problem (e.g., Calendly vs SavvyCal)
77	- Secondary competitors: Different solution, same problem (e.g., Calendly vs Superhuman scheduling)
78	- Indirect competitors: Conflicting approach (e.g., Calendly vs personal assistant)
79	- How each falls short for customers
80
81	### 6. Differentiation
82	- Key differentiators (capabilities alternatives lack)
83	- How you solve it differently
84	- Why that's better (benefits)
85	- Why customers choose you over alternatives
86
87	### 7. Objections & Anti-Personas
88	- Top 3 objections heard in sales and how to address them
89	- Who is NOT a good fit (anti-persona)
90
91	### 8. Switching Dynamics
92	The JTBD Four Forces:
93	- Push: What frustrations drive them away from current solution
94	- Pull: What attracts them to you
95	- Habit: What keeps them stuck with current approach
96	- Anxiety: What worries them about switching
97
98	### 9. Cu

People who liked this also viewed

6 picks

Type

product-marketing

39kinstalls6.5kforks

View on GitHub

How to install product-marketing?

coreyhaines31/marketingskills/product-marketing

$npx -y skills add coreyhaines31/marketingskills --skill product-marketing

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Product Marketing Context
2
3	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.
4
5	The document is stored at `.agents/product-marketing.md`.
6
7	## Workflow
8
9	### Step 1: Check for Existing Context
10
11	First, check if `.agents/product-marketing.md` already exists. Also check `.claude/product-marketing.md` and the legacy filename `product-marketing-context.md` (in either `.agents/` or `.claude/`) for older setups — if found anywhere other than `.agents/product-marketing.md`, offer to move it to the canonical location.
12
13	If it exists:
14	- Read it and summarize what's captured — note its current Document version and the last few Changelog entries so the user sees where the doc stands and what's changed recently
15	- Ask which sections they want to update
16	- Only gather info for those sections
17	- On any substantive save, bump the version and add a changelog entry (see Step 4). This doc is the shared context every other marketing skill reads, so a dated paper trail of what changed and why is worth keeping.
18
19	If it doesn't exist, offer two options:
20
21	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.
22
23	2. Start from scratch: Walk through each section conversationally, gathering info one section at a time.
24
25	Most users prefer option 1. After presenting the draft, ask: "What needs correcting? What's missing?"
26
27	### Step 2: Gather Information
28
29	If auto-drafting:
30	1. Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs
31	2. Draft all sections based on what you find
32	3. Present the draft and ask what needs correcting or is missing
33	4. Iterate until the user is satisfied
34
35	If starting from scratch:
36	Walk through each section below conversationally, one at a time. Don't dump all questions at once.
37
38	For each section:
39	1. Briefly explain what you're capturing
40	2. Ask relevant questions
41	3. Confirm accuracy
42	4. Move to the next
43
44	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.
45
46	---
47
48	## Sections to Capture
49
50	### 1. Product Overview
51	- One-line description
52	- What it does (2-3 sentences)
53	- Product category (what "shelf" you sit on—how customers search for you)
54	- Product type (SaaS, marketplace, e-commerce, service, etc.)
55	- Business model and pricing
56
57	### 2. Target Audience
58	- Target company type (industry, size, stage)
59	- Target decision-makers (roles, departments)
60	- Primary use case (the main problem you solve)
61	- Jobs to be done (2-3 things customers "hire" you for)
62	- Specific use cases or scenarios
63
64	### 3. Personas (B2B only)
65	If multiple stakeholders are involved in buying, capture for each:
66	- User, Champion, Decision Maker, Financial Buyer, Technical Influencer
67	- What each cares about, their challenge, and the value you promise them
68
69	### 4. Problems & Pain Points
70	- Core challenge customers face before finding you
71	- Why current solutions fall short
72	- What it costs them (time, money, opportunities)
73	- Emotional tension (stress, fear, doubt)
74
75	### 5. Competitive Landscape
76	- Direct competitors: Same solution, same problem (e.g., Calendly vs SavvyCal)
77	- Secondary competitors: Different solution, same problem (e.g., Calendly vs Superhuman scheduling)
78	- Indirect competitors: Conflicting approach (e.g., Calendly vs personal assistant)
79	- How each falls short for customers
80
81	### 6. Differentiation
82	- Key differentiators (capabilities alternatives lack)
83	- How you solve it differently
84	- Why that's better (benefits)
85	- Why customers choose you over alternatives
86
87	### 7. Objections & Anti-Personas
88	- Top 3 objections heard in sales and how to address them
89	- Who is NOT a good fit (anti-persona)
90
91	### 8. Switching Dynamics
92	The JTBD Four Forces:
93	- Push: What frustrations drive them away from current solution
94	- Pull: What attracts them to you
95	- Habit: What keeps them stuck with current approach
96	- Anxiety: What worries them about switching
97
98	### 9. Cu

People who liked this also viewed

6 picks

Type