Product Marketing
Create and maintain a shared product-marketing context file so every downstream marketing and analytics skill speaks with one voice about audience, differentiation, and proof.
Overview
Product-marketing is an agent skill most often used in Validate (also Launch and Grow) that builds and maintains `.agents/product-marketing.md` so solo builders have one citable source for audience, differentiation, and
Install
npx skills add https://github.com/coreyhaines31/marketingskills --skill product-marketingWhat is this skill?
- Bootstraps or updates `.agents/product-marketing.md` with structured sections (overview, personas, differentiation, obje
- Offers auto-draft from codebase or conversational walkthrough section by section
- Detects existing context and applies targeted updates when positioning or tiers change
- Aligns customer language and competitive landscape for reuse across marketing skills in the repo
- Eval-driven workflow checks for existing file before creating or patching
- Covers applicable sections including Product Overview, Target Audience, Personas, Competitive Landscape, Differentiation
- Persists context at `.agents/product-marketing.md`
Adoption & trust: 16k installs on skills.sh; 32.4k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are shipping marketing and analytics work without a single, agent-readable brief for who you sell to, what you solve, and how you sound different.
Who is it for?
B2B SaaS or product-led solo builders who want repo-local marketing context before campaigns, landing pages, or tracking plans.
Skip if: Teams that already maintain an equivalent approved positioning doc elsewhere and do not want agents to duplicate or overwrite it without review.
When should I use this skill?
User wants to set up, auto-draft, or update product marketing context for B2B/SaaS positioning and personas.
What do I get? / Deliverables
You get a maintained product-marketing context file other skills can load first—then you invoke analytics, SEO, or campaign skills with shared positioning instead of re-explaining the business.
- `.agents/product-marketing.md` with completed or updated sections
- Section-level update notes when refreshing existing context
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Validate because positioning, personas, objections, and competitive framing are decided before you scale copy, ads, and tracking. Scope subphase fits defining who you serve, what you solve, and how you differ—the inputs every later launch and growth tactic needs.
Where it fits
Define ICP, objections, and differentiation before committing to a landing page structure.
Capture switching dynamics and proof points before packaging new tiers.
Reuse brand voice and customer language when drafting launch announcements.
Refresh proof points and competitive notes after shipping major features.
How it compares
Use instead of one-off chat dumps of positioning when you need a persistent file other marketing skills actually read.
Common Questions / FAQ
Who is product-marketing for?
Solo founders and indie product teams selling SaaS or B2B tools who need structured positioning, personas, and proof in a file agents can reuse across the marketing skill pack.
When should I use product-marketing?
During Validate when scoping audience and differentiation; before Launch when writing distribution copy; and during Grow when refreshing proof points or tiers—any time messaging or ICP changes.
Is product-marketing safe to install?
It writes marketing context under `.agents/` in your project; review generated competitive and customer claims before publishing externally, and check the Security Audits panel on this Prism page before install.
Workflow Chain
Then invoke: analytics
SKILL.md
READMESKILL.md - Product Marketing
{ "skill_name": "product-marketing", "evals": [ { "id": 1, "prompt": "I want to set up my product marketing context. We're a B2B SaaS company that sells a customer feedback platform to product teams.", "expected_output": "Should check if .agents/product-marketing.md already exists. If not, should offer two options: (1) Auto-draft from codebase (recommended) or (2) Start from scratch. If user chooses start from scratch, should walk through sections conversationally one at a time. Should cover all applicable sections: Product Overview, Target Audience, Personas, Problems You Solve, Competitive Landscape, Differentiation, Objections, Switching Dynamics, Customer Language, Brand Voice, Proof Points, and Goals. Should create the file at .agents/product-marketing.md when complete.", "assertions": [ "Checks for existing product-marketing.md", "Offers two options: auto-draft or start from scratch", "Covers applicable sections", "Walks through sections conversationally one at a time", "Creates file at .agents/product-marketing.md" ], "files": [] }, { "id": 2, "prompt": "Update our product marketing context. We just added a new enterprise tier and our target audience has expanded to include VP of Engineering, not just Product Managers.", "expected_output": "Should check for existing .agents/product-marketing.md and read it. Should identify which sections need updating based on the changes: Target Audience (add VP of Engineering), Personas (add new persona), Product Overview (new enterprise tier, including pricing updates within that section), Objections (enterprise-specific), and Competitive Landscape (enterprise competitors). Should update only the relevant sections, preserving existing content that hasn't changed.", "assertions": [ "Reads existing product-marketing.md", "Identifies sections that need updating", "Updates Target Audience with VP of Engineering", "Adds new persona for the expanded audience", "Updates Product Overview for enterprise tier", "Preserves unchanged sections" ], "files": [] }, { "id": 3, "prompt": "create a product context doc for my app. it's a mobile app that helps people find hiking trails. we're just getting started.", "expected_output": "Should trigger on casual phrasing. Should check for existing context doc. Should offer auto-draft or start-from-scratch options. Should adapt questions for an early-stage B2C mobile app (outdoor/fitness niche). Should note that some sections may be sparse for an early-stage product and that's okay — they can be filled in as the business matures. Should skip non-applicable sections (e.g., Personas section is B2B-focused) rather than forcing all 12. Should accept lighter answers for sections like Proof Points or Competitive Landscape if the company is new.", "assertions": [ "Triggers on casual phrasing", "Checks for existing context doc", "Offers auto-draft or start-from-scratch options", "Adapts questions for early-stage B2C mobile app", "Notes some sections may be sparse early on", "Skips non-applicable sections rather than forcing all 12", "Creates file at .agents/product-marketing.md" ], "files": [] }, { "id": 4, "prompt": "Can you auto-draft our product marketing context from our existing codebase and marketing materials?", "expected_output": "Should activate the auto-draft workflow mode. Should scan the codebase for existing marketing context: README, landing page copy, pricing page, about page, meta descriptions, any existing documentation. Should draft the product-marketing.md from what it finds, filling in sections where information is available and flagging sections that need manual input. Should present the draft for review before saving.", "assertions": [