product-marketing-context
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/product-marketing-context.md` that other marketing skills reference.
Best use case
product-marketing-context is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. 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/product-marketing-context.md` that other marketing skills reference.
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/product-marketing-context.md` that other marketing skills reference.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "product-marketing-context" skill to help with this workflow task. Context: 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/product-marketing-context.md` that other marketing skills reference.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/product-marketing-context/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How product-marketing-context Compares
| Feature / Agent | product-marketing-context | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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/product-marketing-context.md` that other marketing skills reference.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agent for Product Research
Browse AI agent skills for product research, competitive analysis, customer discovery, and structured product decision support.
AI Agent for SaaS Idea Validation
Use AI agent skills for SaaS idea validation, market research, customer discovery, competitor analysis, and documenting startup hypotheses.
SKILL.md Source
# 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: ```markdown # 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 | |------|---------| | | | ## Brand Voice **Tone:** **Style:** **Personality:** ## Proof Points **Metrics:** **Customers:** **Testimonials:** > "[quote]" — [who] **Value themes:** | Theme | Proof | |-------|-------| | | | ## Goals **Business goal:** **Conversion action:** **Current metrics:** ``` --- ## Step 4: Confirm and Save - Show the completed document - Ask if anything needs adjustment - Save to `.claude/product-marketing-context.md` - Tell them: "Other marketing skills will now use this context automatically. Run `/product-marketing-context` anytime to update it." --- ## 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 (e.g., Personas for B2C)
Related Skills
deploying-to-production
Automate creating a GitHub repository and deploying a web project to Vercel. Use when the user asks to deploy a website/app to production, publish a project, or set up GitHub + Vercel deployment.
json-to-llm-context
Turn JSON or PostgreSQL jsonb payloads into compact readable context for LLMs. Use when a user wants to compress JSON, reduce token usage, summarize API responses, or convert structured data into model-friendly text without dumping raw paths.
opencontext
Persistent memory and context management for AI agents using OpenContext. Keep context across sessions/repos/dates, store conclusions, and provide document search workflows.
production-code-audit
Autonomously deep-scan entire codebase line-by-line, understand architecture and patterns, then systematically transform it to production-grade, corporate-level professional quality with optimizations
office-productivity
Office productivity workflow covering document creation, spreadsheet automation, presentation generation, and integration with LibreOffice and Microsoft Office formats.
linux-production-shell-scripts
This skill should be used when the user asks to "create bash scripts", "automate Linux tasks", "monitor system resources", "backup files", "manage users", or "write production shell scripts". It provides ready-to-use shell script templates for system administration.
hig-project-context
Create or update a shared Apple design context document that other HIG skills use to tailor guidance. Use when the user says 'set up my project context,' 'what platforms am I targeting,' 'configure HIG settings,' or when starting a new Apple platform project.
ddd-context-mapping
Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.
context7-auto-research
Automatically fetch latest library/framework documentation for Claude Code via Context7 API
context-window-management
Strategies for managing LLM context windows including summarization, trimming, routing, and avoiding context rot Use when: context window, token limit, context management, context engineering, long context.
context-manager
Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems. Orchestrates context across multi-agent workflows, enterprise AI systems, and long-running projects with 2024/2025 best practices. Use PROACTIVELY for complex AI orchestration.
context-management-context-save
Use when working with context management context save