product-marketing · Skill Details

PurposeCreates and maintains a product marketing context document (`.agents/product-marketing.md`) capturing positioning, ICP, and messaging. Method: checks existing doc, auto-drafts from repo or gathers via conversational workflow across 12 sections, then versions and saves. Value: gives all other marketing skills a shared foundation, eliminating repeated questions and tracking positioning evolution.

Domains

MarketingBusiness

Forms

WorkflowBusiness Process

Required Tools

—None

Languages

—No strong dependency

Package Manager

—N/A

Mechanism

When It Triggers · How It Works · What It Produces

Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.

Trigger

When starting any new marketing project, or when the user mentions 'product context', 'positioning', 'ICP', 'target audience', or wants to avoid repeating foundational info across marketing tasks.

Mechanism

Check for an existing .agents/product-marketing.md (and legacy locations); read or offer to migrate it.
If absent, auto-draft from the codebase (README, landing pages, package.json) or walk sections conversationally.
Gather 12 structured sections (overview, audience, personas, pain points, competition, differentiation, objections, switching forces, customer language, voice, proof, goals).
Write the doc, bump version, prepend a dated changelog entry on substantive changes, and save to .agents/product-marketing.md.

Result

A shared product-marketing.md context file that all other marketing skills reference automatically, eliminating repeated foundational questions and keeping a versioned paper trail of positioning evolution.

Use Cases

Two Typical Use Cases

Scenario 01

Founder sets shared marketing context

A founder is about to run ads, emails, and a launch but is tired of re-explaining their product to each skill. They run /product-marketing, which auto-drafts a context doc from their repo. After a quick review, all downstream marketing skills read the same positioning, ICP, and customer language — saving hours and keeping messaging consistent across channels.

Scenario 02

Marketing lead updates positioning post-interviews

A marketing lead notices positioning has drifted after customer interviews. They run /product-marketing to update the doc: revise value prop, add objections, bump to v3 with a changelog entry. Every other skill now generates against the new context, and the changelog shows exactly how and why the positioning evolved for the team.

Skill File

SKILL.md

Open in GitHub ↗

SKILL.mdLoading from GitHub…

Skill Composition

Open in GitHub ↗

SKILL.md50.0%
other50.0%

▸skills/product-marketing/
▸root
- ·SKILL.md
- ▸evals
  - ·evals.json

Per the Agent Skills spec, SKILL.md is the only required file. The colored bars classify the rest into the three spec-aligned optional directories (scripts / references / assets) and an 'other' bucket. The full directory tree is below.