Agent skill · marketing growth · aiskillstore
product-marketing
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 to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
Why this skill is useful
Creates a structured product marketing context document that consolidates essential positioning and messaging information for marketing tasks.
What it needs
About 6k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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.md. Workflow Step 1: Check for Existing Context 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. If it exists: 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 Ask which sections they want to update Only gather info for those sections 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. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/product-marketing