product-marketing · 스킬 지원 에이전트
제품의 대상 고객, 해결 문제와 차별점을 정리해 이후 작업에서 반복해서 참고할 문서를 만듭니다.
새 글을 쓸 때마다 우리 서비스가 무엇인지 설명하고 있다면 먼저 써볼 스킬입니다. 제품 기능뿐 아니라 누구의 어떤 불편을 해결하는지, 대안과 어떤 차이가 있는지를 한 곳에 모읍니다.
공식 설명, 고객 반응과 확인된 기능을 제공하면 빠진 정보를 질문하며 맥락을 정리합니다. 다른 마케팅 스킬이 이 문서를 참고하므로 추정과 사실을 구분해서 작성하세요. 제품이 바뀌었을 때 문서도 함께 갱신하면 후속 초안의 일관성을 유지하기 쉽습니다.
product-marketing으로 우리 자료 모음집의 제품 맥락 문서를 만들어줘. 대상, 해결 문제, 실제 기능, 대안과 차이를 정리하고 모르는 정보는 질문해줘.
받을 수 있는 결과다른 마케팅 스킬이 참고할 제품 맥락 문서
스킬 지원 에이전트가 필요합니다. 생성된 .agents/product-marketing.md와 관련 맥락 파일을 함께 관리합니다.
현재 사용 중인 스킬 지원 에이전트에 아래 요청을 붙여넣으세요. SKILL.md만 복사하면 보조 파일이 빠질 수 있어요.
https://github.com/coreyhaines31/marketingskills 에서 skills/product-marketing 스킬을 현재 에이전트의 스킬 폴더에 설치해줘. SKILL.md와 이 스킬이 참조하는 scripts·references·assets와 공통 파일을 함께 유지하고, 필요한 실행 환경과 추가 연결을 확인한 뒤 알려줘. 설치가 끝나면 product-marketing 스킬을 인식하는지 확인해줘.
“product-marketing 스킬을 사용해줘. 입력 자료: 제품 기능·고객·경쟁 대안·실제 근거”처럼 요청하세요. 위의 예시를 내 자료에 맞게 바꿔도 좋아요.
예상 결과는 ‘다른 마케팅 스킬이 참고할 제품 맥락 문서’입니다. 필요한 내용이 포함됐는지 확인하세요. 입력 자료의 사실·숫자와 결과를 대조하고, 부족한 부분을 이어서 요청하세요.
제작자 원본 2026-10-04 확인 · 설치 안내 2026-10-04 확인 · 실제 설치·실행 미검증
모델 사용 요금과 연결 앱 요금은 이용 중인 서비스의 정책을 따릅니다.
설치 안내 출처--- name: product-marketing description: "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." metadata: version: 2.1.0 --- # 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.--- name: product-marketing description: "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." metadata: version: 2.1.0 --- # 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. 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.md` with this structure: ```markdown # Product Marketing Context **Document version:** v1 **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:** ## Changelog *Newest first. One line per revision: what changed and why.* - v1 ([date]) — Initial context. ``` --- ## Step 4: Confirm, Version, and Save - Show the completed document - Ask if anything needs adjustment - **Set the version and changelog** — this is the paper trail for a doc every other skill reads: - **New document:** set `Document version: v1` and a single Changelog entry — `- v1 ([today]) — Initial context.` - **Updating an existing document:** increment the version (v2 → v3 …), update `Last updated` to today, and **prepend a new Changelog entry** at the top of the list (newest first) summarizing *what changed and why* in one line. Never rewrite or reorder past entries. - A good entry names the sections touched and the reason, not "updated the doc." Examples: - `- v3 (2026-07-16) — Repositioned from "email tool" to "deliverability platform"; added RevOps to the ICP.` - `- v2 (2026-06-02) — Rewrote value prop and objections after 5 customer interviews; added competitor Acme.` - Use today's date in ISO form (YYYY-MM-DD) for the entry and `Last updated`. - **Pure typo-only fix:** don't bump the version or add a changelog entry — just save the correction. Every other change bumps the version and gets an entry. When the change is a real repositioning, say so plainly — downstream skills will now generate against the new context. - Save to `.agents/product-marketing.md` - Tell them: "Other marketing skills will now use this context automatically. The Changelog at the bottom tracks every revision — check it to see how your positioning has evolved. Run `/product-marketing` 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)
Original skill: coreyhaines31/marketingskills/skills/product-marketing/SKILL.md Source: https://github.com/coreyhaines31/marketingskills/blob/dda3841f0b294e01e93b1541486beefbfab0915e/skills/product-marketing/SKILL.md License: MIT MIT License Copyright (c) 2025 Corey Haines Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
SKILL.md 본문입니다. 원문에서 참조하는 스크립트·보조 파일은 원본 패키지에 포함되어 있습니다.