product-marketing-context
by coreyhaines31Guided skill for creating and maintaining a reusable product marketing context document that defines your product overview, ICP, personas, messaging, differentiation, and goals in `.agents/product-marketing-context.md`, so other marketing skills and agents can reuse the same foundation without asking you the same questions every time.
Overview
What this skill does
The product-marketing-context skill helps you create and maintain a single, reusable product marketing context document for your project.
Instead of re-explaining your product, audience, and positioning for every new task, this skill walks you through a structured questionnaire and saves the output to:
.agents/product-marketing-context.md
Other compatible marketing skills and agents then read this file to understand your product, so they can generate content, campaigns, and launch materials that stay on-message.
Who it is for
Use product-marketing-context if you are:
- A founder or product owner defining your product’s story for the first time
- A product marketer or marketing manager who wants consistent messaging across campaigns
- A developer wiring up a system of marketing skills and agents that share a common context file
It is especially useful when you work on:
- Ongoing content marketing (blogs, emails, ads, landing pages)
- Product launches and tier updates
- Positioning or ICP / persona refinement
Problems it solves
The product-marketing-context skill is designed to solve these recurring issues:
- Repeating the same product description and audience details across multiple conversations
- Inconsistent messaging between different agents or skills
- Missing or scattered product marketing notes in many different files
- Hard-to-maintain positioning docs that never get updated
By centralizing this into .agents/product-marketing-context.md, you get a living document that covers:
- Product overview and value proposition
- Target audience and ICP
- Personas and roles involved in the buying process
- Problems you solve and jobs-to-be-done
- Competitive landscape and differentiation
- Objections, switching dynamics, and proof points
- Customer language, brand voice, and marketing goals
When it is or isn’t a good fit
Use product-marketing-context when:
- You are starting a new project and want a strong foundation before using other marketing skills
- You’ve changed your pricing, tiers, or audience (for example, adding an enterprise tier or new buyer roles)
- You are setting up an AI-driven marketing workflow that needs shared context
It may not be a good fit when:
- You only need a one-off piece of copy and don’t plan to reuse the context
- Your product is extremely early and you have no clarity at all yet (you may want to sketch the basics first, then run this skill)
If you intend to do more than one marketing task, installing product-marketing-context first usually pays off quickly.
How to Use
Installation
To add the product-marketing-context skill to your environment, run:
npx skills add https://github.com/coreyhaines31/marketingskills --skill product-marketing-context
``
This pulls the `product-marketing-context` skill from the `coreyhaines31/marketingskills` repository and makes it available alongside any other skills you install from the same source.
After installation, you can open the skill files directly in your editor to review the behavior and adapt your workflows as needed:
- `skills/product-marketing-context/SKILL.md`
- `skills/product-marketing-context/evals/evals.json`
### Core workflow
The product-marketing-context skill follows a clear, two-path workflow based on whether a context file already exists.
#### 1. Check for existing context
When invoked, the skill first looks for an existing context document:
- Primary location: `.agents/product-marketing-context.md`
- Legacy location: `.claude/product-marketing-context.md` (for older setups)
If an older file exists only under `.claude/`, the skill is designed to offer moving or upgrading it into `.agents/` so your setup stays consistent.
#### 2. If the context file exists
If `.agents/product-marketing-context.md` is already present, the skill will:
1. Read and summarize the current contents
2. Ask which sections you want to update (for example, Target Audience, Personas, or Differentiation)
3. Only walk through the selected sections, so you don’t have to repeat everything
This makes it easy to handle incremental updates, such as:
- Expanding your target audience (e.g., now including VP of Engineering)
- Adding a new plan or tier (e.g., an enterprise plan)
- Updating proof points, logos, or case studies
#### 3. If the context file does not exist
If no context file is found, the skill offers two paths:
1. **Auto-draft from codebase (recommended)**
- The skill inspects your repository (for example: `README`, landing pages, marketing copy, `package.json`, etc.)
- It drafts a first version of your product marketing context based on what it finds
- You review, correct, and expand this V1 draft
2. **Start from scratch**
- The skill walks you through each section one at a time in a conversational way
- You answer targeted questions about your product, audience, and positioning
In both cases, once the process is complete, the skill writes the final document to:
- `.agents/product-marketing-context.md`
### Sections captured in the context file
The context file created by product-marketing-context is structured around practical, reusable sections. According to the bundled evaluations, the skill is expected to cover at least the following areas where relevant:
- **Product Overview** – What you sell, what it does, and who it’s for
- **Target Audience** – Your ICP, roles, industries, and company sizes
- **Personas** – Key stakeholders such as Product Managers, VPs, founders, or buyers
- **Problems You Solve** – Pain points, jobs-to-be-done, and use cases
- **Competitive Landscape** – Who you compete with and how buyers see alternatives
- **Differentiation** – What makes your product meaningfully different
- **Objections** – Common reasons prospects hesitate or say no
- **Switching Dynamics** – What has to happen for someone to switch to you
- **Customer Language** – Phrases, quotes, and vocabulary your customers actually use
- **Brand Voice** – How you want to sound across channels
- **Proof Points** – Testimonials, metrics, social proof, and case studies
- **Goals** – What success looks like for your marketing and go-to-market efforts
Not every section must be filled out for every product, but the skill is designed to cover all applicable sections and prompt you where information is missing.
### Using the context in your workflows
Once `.agents/product-marketing-context.md` exists, you can:
- Reference it when running other **marketing-related skills** so they share the same understanding of your product
- Keep it under version control in your repository to track how your positioning evolves
- Use it as an internal source of truth for new teammates or collaborators
Because the file lives at a predictable path, it is easy for:
- Other agents in the `marketingskills` collection
- Custom tools or scripts you write
…to load it and work with a consistent product marketing foundation.
### Files and directories to inspect
For deeper understanding or customization, start with:
- `SKILL.md` – Core skill definition, description, and workflow details
- `evals/evals.json` – Example prompts and expected behavior, useful to see how the skill should respond in real scenarios
You can adapt the skill’s behavior (for example, how you call it or chain it with others) to fit your own repository structure and automation tools.
## FAQ
### What is product-marketing-context in simple terms?
The product-marketing-context skill is a guided assistant that helps you create a structured product marketing document—stored at `.agents/product-marketing-context.md`—covering your product, audience, positioning, and key messaging so other skills and agents can reuse it.
### How do I install product-marketing-context?
Install it from the `coreyhaines31/marketingskills` repository with:
```bash
npx skills add https://github.com/coreyhaines31/marketingskills --skill product-marketing-context
After installation, you can view SKILL.md in the product-marketing-context directory to see the exact workflow.
Where is the context document stored?
By default, the skill creates and maintains your product marketing context at:
.agents/product-marketing-context.md
It can also detect older setups at .claude/product-marketing-context.md and offer to migrate them into .agents/.
What happens if I already have a product-marketing-context file?
If .agents/product-marketing-context.md already exists, the skill will:
- Read and summarize the content
- Ask which sections you want to change
- Only gather new information for those sections
This prevents you from having to re-answer questions that are already documented.
Can product-marketing-context update my context when my product changes?
Yes. The skill is designed to support incremental updates. For example, if you:
- Add a new enterprise tier
- Expand your target audience to new roles (e.g., adding VP of Engineering)
- Adjust your differentiation or proof points
…you can invoke the skill, and it will help you update only the relevant sections in .agents/product-marketing-context.md.
Does this skill draft content automatically from my codebase?
It can. When no context file exists, product-marketing-context offers an auto-draft from codebase option. In that mode, it reviews available materials in your repo (such as README, marketing copy, or package metadata) to draft a first version that you then refine.
How does product-marketing-context work with other marketing skills?
Other marketing-focused skills in your setup can read .agents/product-marketing-context.md to:
- Understand your product and ICP
- Reuse your brand voice and messaging
- Stay aligned with your positioning and goals
You typically run product-marketing-context first on a new project, then rely on the shared context file when you generate emails, landing pages, launch announcements, or other assets.
Is product-marketing-context useful for developers?
Yes. Developers who are wiring up multi-skill workflows can treat .agents/product-marketing-context.md as a single source of truth that:
- Lives in the repository
- Is easy to parse or load programmatically
- Keeps all marketing-related skills aligned
This is especially helpful in larger automation setups where different agents need consistent product and audience information.
What files should I look at to understand or customize the skill?
Start with:
SKILL.md– Describes the purpose of product-marketing-context and its workflowevals/evals.json– Shows example prompts and expected outputs, which help you see how the skill behaves in real-world scenarios
You can then adapt how you call the skill, or chain it with others, to match your own repository structure and marketing processes.
