product-marketing-context

Name: product-marketing-context
Author: mysticaltech

324stars85forks

How to install product-marketing-context?

mysticaltech/marketingskills/product-marketing-context

$npx -y skills add mysticaltech/marketingskills --skill product-marketing-context

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,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude

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 `.claude/product-marketing-context.md`.
6
7	## Workflow
8
9	### Step 1: Check for Existing Context
10
11	First, check if `.claude/product-marketing-context.md` already exists.
12
13	If it exists:
14	- Read it and summarize what's captured
15	- Ask which sections they want to update
16	- Only gather info for those sections
17
18	If it doesn't exist, offer two options:
19
20	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.
21
22	2. Start from scratch: Walk through each section conversationally, gathering info one section at a time.
23
24	Most users prefer option 1. After presenting the draft, ask: "What needs correcting? What's missing?"
25
26	### Step 2: Gather Information
27
28	If auto-drafting:
29	1. Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs
30	2. Draft all sections based on what you find
31	3. Present the draft and ask what needs correcting or is missing
32	4. Iterate until the user is satisfied
33
34	If starting from scratch:
35	Walk through each section below conversationally, one at a time. Don't dump all questions at once.
36
37	For each section:
38	1. Briefly explain what you're capturing
39	2. Ask relevant questions
40	3. Confirm accuracy
41	4. Move to the next
42
43	Important: Push for verbatim customer language. Exact phrases are more valuable than polished descriptions.
44
45	---
46
47	## Sections to Capture
48
49	### 1. Product Overview
50	- One-line description
51	- What it does (2-3 sentences)
52	- Product category (what "shelf" you sit on—how customers search for you)
53	- Product type (SaaS, marketplace, e-commerce, service, etc.)
54	- Business model and pricing
55
56	### 2. Target Audience
57	- Target company type (industry, size, stage)
58	- Target decision-makers (roles, departments)
59	- Primary use case (the main problem you solve)
60	- Jobs to be done (2-3 things customers "hire" you for)
61	- Specific use cases or scenarios
62
63	### 3. Personas (B2B only)
64	If multiple stakeholders are involved in buying, capture for each:
65	- User, Champion, Decision Maker, Financial Buyer, Technical Influencer
66	- What each cares about, their challenge, and the value you promise them
67
68	### 4. Problems & Pain Points
69	- Core challenge customers face before finding you
70	- Why current solutions fall short
71	- What it costs them (time, money, opportunities)
72	- Emotional tension (stress, fear, doubt)
73
74	### 5. Competitive Landscape
75	- Direct competitors: Same solution, same problem (e.g., Calendly vs SavvyCal)
76	- Secondary competitors: Different solution, same problem (e.g., Calendly vs Superhuman scheduling)
77	- Indirect competitors: Conflicting approach (e.g., Calendly vs personal assistant)
78	- How each falls short for customers
79
80	### 6. Differentiation
81	- Key differentiators (capabilities alternatives lack)
82	- How you solve it differently
83	- Why that's better (benefits)
84	- Why customers choose you over alternatives
85
86	### 7. Objections & Anti-Personas
87	- Top 3 objections heard in sales and how to address them
88	- Who is NOT a good fit (anti-persona)
89
90	### 8. Switching Dynamics
91	The JTBD Four Forces:
92	- Push: What frustrations drive them away from current solution
93	- Pull: What attracts them to you
94	- Habit: What keeps them stuck with current approach
95	- Anxiety: What worries them about switching
96
97	### 9. Customer Language
98	- How customers describe the problem (verbatim)
99	- How they describe your solution (verbatim)
100	- Words/phrases to use
101	- Words/phrases to avoid
102	- Glossary of product-specific terms
103
104	### 10. Brand Voice
105	- Tone (professional, casual, playful, etc.)
106	- Communication style (direct, conversational, technical)
107	- Brand personality (3-5 adjectives)
108
109	### 11. Proof Points
110	- Key metrics or results to cite
111	- Notable customers/logos
112	- Testimonial snippets
113	- Main value themes and supporting evidence
114
115	### 12. Goals
116	- Primary business goal
117	- Key conversion action (what you want people to do)
118	- Current metrics (if known)
119
120	---
121
122	## Step 3: Create the Document
123
124	After gathering information, create `.claude/product-marketing-context.md` with this structure:
125
126	```markdown
127	# Product Marketing Context
128
129	Last updated: [date]
130
131	## Product Overview
132	One-liner:
133	What it does:
134	Product category:
135	**

People who liked this also viewed

6 picks

Type

product-marketing-context

324stars85forks

View on GitHub

How to install product-marketing-context?

mysticaltech/marketingskills/product-marketing-context

$npx -y skills add mysticaltech/marketingskills --skill product-marketing-context

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 `.claude/product-marketing-context.md`.
6
7	## Workflow
8
9	### Step 1: Check for Existing Context
10
11	First, check if `.claude/product-marketing-context.md` already exists.
12
13	If it exists:
14	- Read it and summarize what's captured
15	- Ask which sections they want to update
16	- Only gather info for those sections
17
18	If it doesn't exist, offer two options:
19
20	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.
21
22	2. Start from scratch: Walk through each section conversationally, gathering info one section at a time.
23
24	Most users prefer option 1. After presenting the draft, ask: "What needs correcting? What's missing?"
25
26	### Step 2: Gather Information
27
28	If auto-drafting:
29	1. Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs
30	2. Draft all sections based on what you find
31	3. Present the draft and ask what needs correcting or is missing
32	4. Iterate until the user is satisfied
33
34	If starting from scratch:
35	Walk through each section below conversationally, one at a time. Don't dump all questions at once.
36
37	For each section:
38	1. Briefly explain what you're capturing
39	2. Ask relevant questions
40	3. Confirm accuracy
41	4. Move to the next
42
43	Important: Push for verbatim customer language. Exact phrases are more valuable than polished descriptions.
44
45	---
46
47	## Sections to Capture
48
49	### 1. Product Overview
50	- One-line description
51	- What it does (2-3 sentences)
52	- Product category (what "shelf" you sit on—how customers search for you)
53	- Product type (SaaS, marketplace, e-commerce, service, etc.)
54	- Business model and pricing
55
56	### 2. Target Audience
57	- Target company type (industry, size, stage)
58	- Target decision-makers (roles, departments)
59	- Primary use case (the main problem you solve)
60	- Jobs to be done (2-3 things customers "hire" you for)
61	- Specific use cases or scenarios
62
63	### 3. Personas (B2B only)
64	If multiple stakeholders are involved in buying, capture for each:
65	- User, Champion, Decision Maker, Financial Buyer, Technical Influencer
66	- What each cares about, their challenge, and the value you promise them
67
68	### 4. Problems & Pain Points
69	- Core challenge customers face before finding you
70	- Why current solutions fall short
71	- What it costs them (time, money, opportunities)
72	- Emotional tension (stress, fear, doubt)
73
74	### 5. Competitive Landscape
75	- Direct competitors: Same solution, same problem (e.g., Calendly vs SavvyCal)
76	- Secondary competitors: Different solution, same problem (e.g., Calendly vs Superhuman scheduling)
77	- Indirect competitors: Conflicting approach (e.g., Calendly vs personal assistant)
78	- How each falls short for customers
79
80	### 6. Differentiation
81	- Key differentiators (capabilities alternatives lack)
82	- How you solve it differently
83	- Why that's better (benefits)
84	- Why customers choose you over alternatives
85
86	### 7. Objections & Anti-Personas
87	- Top 3 objections heard in sales and how to address them
88	- Who is NOT a good fit (anti-persona)
89
90	### 8. Switching Dynamics
91	The JTBD Four Forces:
92	- Push: What frustrations drive them away from current solution
93	- Pull: What attracts them to you
94	- Habit: What keeps them stuck with current approach
95	- Anxiety: What worries them about switching
96
97	### 9. Customer Language
98	- How customers describe the problem (verbatim)
99	- How they describe your solution (verbatim)
100	- Words/phrases to use
101	- Words/phrases to avoid
102	- Glossary of product-specific terms
103
104	### 10. Brand Voice
105	- Tone (professional, casual, playful, etc.)
106	- Communication style (direct, conversational, technical)
107	- Brand personality (3-5 adjectives)
108
109	### 11. Proof Points
110	- Key metrics or results to cite
111	- Notable customers/logos
112	- Testimonial snippets
113	- Main value themes and supporting evidence
114
115	### 12. Goals
116	- Primary business goal
117	- Key conversion action (what you want people to do)
118	- Current metrics (if known)
119
120	---
121
122	## Step 3: Create the Document
123
124	After gathering information, create `.claude/product-marketing-context.md` with this structure:
125
126	```markdown
127	# Product Marketing Context
128
129	Last updated: [date]
130
131	## Product Overview
132	One-liner:
133	What it does:
134	Product category:
135	**

People who liked this also viewed

6 picks

Type