Product Marketing Context
When the user wants to create or update their product marketing context document.
Install
npx skills add LeoYeAI/agent-master-skills --skill product-marketing-context -g -a claude-code -y- Repository
- LeoYeAI/agent-master-skills2.2k
- Category
- AI and agents
- Updated
- 4d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'service context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'describe my service,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Works for products, services, or hybrid offerings, B2B and B2C. 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 offering, audience, and positioning 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. Works for products, services, or hybrid offerings, B2B and B2C alike.
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:
-
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.
-
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:
- Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs
- Draft all sections based on what you find
- Present the draft and ask what needs correcting or is missing
- 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:
- Briefly explain what you're capturing
- Ask relevant questions using the right question format (see below)
- Confirm accuracy
- Move to the next
