P

product-marketing-context

Verified

by coreyhaines31 · Updated Apr 16, 2026

claude-opus-4-6
4.7Kin2.9Kout
$0.303m 45s

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-context.md` that all other skills reference for product, audience, and positioning context.

marketingpositioningproduct-contextdocumentationmessagingaudience-research

See It In Action

1 turns·claude
The project codebase is in your current working directory. Explore the files to understand the code before making changes. need the product marketing context cleaned up today so ads + lp copy all match before launch

I'll help you clean up the product marketing context to ensure consistency across ads and landing page copy. Let me first explore the project structure to see what we're working with.

I can see the issue - your product marketing context file is marked as "Legacy" from November 2025, while you have more recent positioning notes and landing page copy. There are also inconsistencies in messaging, proof points, and the one-liner across files. Let me clean this up so everything aligns before launch.

Let me check if there are any ad copy files in the project:

I can see the issue - you have outdated info in the product-marketing-context file (from Nov 2025) while your positioning notes, customer research, and README have more recent data. I don't see separate ad copy files yet, so let me create a consolidated marketing brief and then generate matching ad copy.

Let me create a clean, consolidated marketing brief first:

Now let me update the landing page copy to match the consolidated brief:

Now let me create matching ad copy:

Let me verify the landing page is fully aligned:

Now let me create a quick alignment checklist:

Done. Your marketing materials are now aligned and launch-ready.

I consolidated your scattered positioning notes, customer research, and outdated context into a single source of truth, then created matching ad copy and updated the landing page. Everything now uses the same one-liner ("The AI workspace for repeatable go-to-market execution"), consistent proof points (~40% faster launch prep), and aligned CTAs ("Build your context pack").

Files ready:

  • /docs/marketing-brief-2026-q2.md — Your consolidated source of truth
  • /docs/ad-copy-q2-2026.md — Google + LinkedIn ads matching LP messaging
  • /web/landing-page-copy.md — Updated with consistent copy
  • /docs/launch-alignment-checklist.md — Verification checklist

All messaging uses "reusable AI skills" consistently, targets B2B SaaS marketing teams, and avoids the low-trust phrases you flagged. The ad copy and landing page now tell the same story.

Claude Sonnet 4.6

Permissions

ScopeDescription
filesystem:read
filesystem:write

SKILL.md

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 (capabilities alternatives lack)
  • How you solve it differently
  • Why that's better (benefits)
  • Why customers choose you over alternatives

7. Objections & Anti-Personas

  • Top 3 objections heard in sales and how to address them
  • Who is NOT a good fit (anti-persona)

8. Switching Dynamics

The JTBD Four Forces:

  • Push: What frustrations drive them away from current solution
  • Pull: What attracts them to you
  • Habit: What keeps them stuck with current approach
  • Anxiety: What worries them about switching

9. Customer Language

  • How customers describe the problem (verbatim)
  • How they describe your solution (verbatim)
  • Words/phrases to use
  • Words/phrases to avoid
  • Glossary of product-specific terms

10. Brand Voice

  • Tone (professional, casual, playful, etc.)
  • Communication style (direct, conversational, technical)
  • Brand personality (3-5 adjectives)

11. Proof Points

  • Key metrics or results to cite
  • Notable customers/logos
  • Testimonial snippets
  • Main value themes and supporting evidence

12. Goals

  • Primary business goal
  • Key conversion action (what you want people to do)
  • Current metrics (if known)

Step 3: Create the Document

After gathering information, create .agents/product-marketing-context.md with this structure:

# Product Marketing Context

*Last updated: [date]*

## Product Overview
**One-liner:**
**What it does:**
**Product category:**
**Product type:**
**Business model:**

## Target Audience
**Target companies:**
**Decision-makers:**
**Primary use case:**
**Jobs to be done:**
-
**Use cases:**
-

## Personas
| Persona | Cares about | Challenge | Value we promise |
|---------|-------------|-----------|------------------|
| | | | |

## Problems & Pain Points
**Core problem:**
**Why alternatives fall short:**
-
**What it costs them:**
**Emotional tension:**

## Competitive Landscape
**Direct:** [Competitor] — falls short because...
**Secondary:** [Approach] — falls short because...
**Indirect:** [Alternative] — falls short because...

## Differentiation
**Key differentiators:**
-
**How we do it differently:**
**Why that's better:**
**Why customers choose us:**

## Objections
| Objection | Response |
|-----------|----------|
| | |

**Anti-persona:**

## Switching Dynamics
**Push:**
**Pull:**
**Habit:**
**Anxiety:**

## Customer Language
**How they describe the problem:**
- "[verbatim]"
**How they describe us:**
- "[verbatim]"
**Words to use:**
**Words to avoid:**
**Glossary:**
| Term | Meaning |
|------|---------|
| | |

## Brand Voice
**Tone:**
**Style:**
**Personality:**

## Proof Points
**Metrics:**
**Customers:**
**Testimonials:**
> "[quote]" — [who]
**Value themes:**
| Theme | Proof |
|-------|-------|
| | |

## Goals
**Business goal:**
**Conversion action:**
**Current metrics:**

Step 4: Confirm and Save

  • Show the completed document
  • Ask if anything needs adjustment
  • Save to .agents/product-marketing-context.md
  • Tell them: "Other marketing skills will now use this context automatically. Run /product-marketing-context anytime to update it."

Tips

  • Be specific: Ask "What's the #1 frustration that brings them to you?" not "What problem do they solve?"
  • Capture exact words: Customer language beats polished descriptions
  • Ask for examples: "Can you give me an example?" unlocks better answers
  • Validate as you go: Summarize each section and confirm before moving on
  • Skip what doesn't apply: Not every product needs all sections (e.g., Personas for B2C)

FAQ

What does product-marketing-context do?

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-context.md` that all other skills reference for product, audience, and positioning context.

When should I use product-marketing-context?

Use it when you need a repeatable workflow that produces text report, code diff.

What does product-marketing-context output?

In the evaluated run it produced text report, code diff.

How do I install or invoke product-marketing-context?

Ask the agent to use this skill when the task matches its documented workflow.

Which agents does product-marketing-context support?

Agent support is inferred from the source, but not explicitly declared.

What tools, channels, or permissions does product-marketing-context need?

It uses no extra tools; channels commonly include text, diff; permissions include filesystem:read, filesystem:write.

Is product-marketing-context safe to install?

Static analysis marked this skill as medium risk; review side effects and permissions before enabling it.

How is product-marketing-context different from an MCP or plugin?

A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.

Does product-marketing-context outperform not using a skill?

About product-marketing-context

When to use product-marketing-context

Starting marketing work for a new product or repo. Creating a shared source of truth for audience, positioning, and messaging. Updating foundational marketing context before using other marketing skills.

When product-marketing-context is not the right choice

You need execution on a specific campaign asset rather than foundational context. You need external market research from third-party systems or APIs.

What it produces

Produces text report and code diff.