Product Marketing Context
Create `.agents/product-marketing-context.md` once so positioning, ICP, and product facts feed every later marketing skill without repeating yourself.
Overview
Product Marketing Context is a journey-wide agent skill that builds `.agents/product-marketing-context.md` so solo builders set positioning and ICP once before every other marketing task.
Install
npx skills add https://github.com/coreyhaines31/marketingskills --skill product-marketing-contextWhat is this skill?
- Creates or updates `.agents/product-marketing-context.md` as the shared source for other marketing skills
- Step 1 checks existing context and supports migration from legacy `.claude/product-marketing-context.md`
- Offers auto-draft from codebase (README, landing, package metadata) when no document exists
- Explicit triggers: product context, ICP, ideal customer profile, positioning, target audience
- Stored path `.agents/product-marketing-context.md`
- Skill metadata version 1.1.0
Adoption & trust: 61.5k installs on skills.sh; 32.4k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You keep re-explaining your product, audience, and positioning to the agent for each marketing chore instead of reusing one trusted context file.
Who is it for?
New Prism or marketing-skill projects where no shared positioning doc exists yet, or when ICP and messaging changed after a pivot.
Skip if: One-off tactical edits when `.agents/product-marketing-context.md` is already accurate and you only need a single ad or keyword list without touching positioning.
When should I use this skill?
User wants product or marketing context, positioning, ICP, target audience, or to set up context before other marketing skills; also when mentioning 'set up context' or 'describe my product'.
What do I get? / Deliverables
You get a maintained product marketing context document other skills reference, with optional codebase auto-draft and selective section updates when the file already exists.
- `.agents/product-marketing-context.md` with positioning, audience, and messaging sections
- Summary of existing context and targeted section updates when revising
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Draft ICP and value prop from README before you commit to a landing page structure.
Align in-app copy and public docs with the same positioning bullets stored in product-marketing-context.
Feed consistent product definitions into SEO skills without re-answering audience questions.
Refresh positioning sections after pricing or segment pivot before email or nurture workflows.
Capture early audience hypotheses in structured form before competitor research deepens.
How it compares
Use before campaign-specific marketing skills—it is the shared context layer, not a distribution or SEO execution skill.
Common Questions / FAQ
Who is product-marketing-context for?
Solo founders and indie builders using marketing agent skills who need a single positioning and audience file every downstream skill can read.
When should I use product-marketing-context?
Use at project kickoff in Validate to scope ICP and positioning; revisit before Launch distribution or Grow lifecycle work when messaging drifts; run first on any new repo before other marketingskills.
Is product-marketing-context safe to install?
Review the Security Audits panel on this Prism page; the skill reads your repo and writes a local markdown context file under `.agents/`.
SKILL.md
READMESKILL.md - Product Marketing 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 `.agents/product-marketing-context.md`. ## Workflow ### Step 1: Check for Existing Context First, check if `.agents/product-marketing-context.md` already exists. Also check `.claude/product-marketing-context.md` for older setups — if found there but not in `.agents/`, offer to move it. **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 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. --- ## 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 (capab