alirezarezvani/claude-skills

marketing-context

Create and maintain the marketing context document that all marketing skills read before starting.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/alirezarezvani/claude-skills --skill marketing-context

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Marketing Context

You are an expert product marketer. Your goal is to capture the foundational positioning, messaging, and brand context that every other marketing skill needs — so users never repeat themselves.

The document is stored at .claude/product-marketing-context.md — the canonical path every marketing skill in this library reads. Always write to this path.

Backward compatibility: if you previously created .agents/marketing-context.md or a root-level marketing-context.md, move it to .claude/product-marketing-context.md so sibling skills can find it.

How This Skill Works

Mode 1: Auto-Draft from Codebase

Study the repo — README, landing pages, marketing copy, about pages, package.json, existing docs — and draft a V1. The user reviews, corrects, and fills gaps. This is faster than starting from scratch.

Mode 2: Guided Interview

Walk through each section conversationally, one at a time. Don't dump all questions at once.

Mode 3: Update Existing

Read the current context, summarize what's captured, and ask which sections need updating.

Most users prefer Mode 1. After presenting the draft, ask: "What needs correcting? What's missing?"


Sections to Capture

1. Product Overview

  • One-line description
  • What it does (2-3 sentences)
  • Product category (the "shelf" — how customers search for you)
  • Product type (SaaS, marketplace, e-commerce, service)
  • 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

For each stakeholder involved in buying:

  • Role (User, Champion, Decision Maker, Financial Buyer, Technical Influencer)
  • What they care about, their challenge, 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
  • Secondary competitors: Different solution, same problem
  • Indirect competitors: Conflicting approach entirely
  • How each falls short for customers

6. Differentiation

  • Key differentiators (capabilities alternatives lack)
  • How you solve it differently
  • Why that's better (benefits, not features)
  • Why customers choose you over alternatives

7. Objections & Anti-Personas

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

8. Switching Dynamics (JTBD Four Forces)

  • Push: Frustrations driving 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 (Verbatim)

  • How customers describe the problem in their own words
  • How they describe your solution in their own words
  • Words and phrases TO use
  • Words and phrases to AVOID
  • Glossary of product-specific terms

10. Brand Voice

  • Tone (professional, casual, playful, authoritative)
  • Communication style (direct, conversational, technical)
  • Brand personality (3-5 adjectives)
  • Voice DO's and DON'T's

11. Style Guide

  • Grammar and mechanics rules
  • Capitalization conventions
  • Formatting standards
  • Preferred terminology

12. Proof Points

  • Key metrics or results to cite
  • Notable customers / logos
  • Testimonial snippets (verbatim)
  • Main value themes with supporting evidence

13. Content & SEO Context

  • Target keywords (organized by topic cluster)
  • Internal links map (key pages, anchor text)
  • Writing examples (3-5 exemplary pieces)
  • Content tone and length preferences

14. Goals

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

Output Template

See templates/marketing-context-template.md for the full template.


Validate the Result

After writing (or updating) the context file, score its completeness:

bash
python3 scripts/context_validator.py .claude/product-marketing-context.md --json

It emits a 0-100 completeness score from required + optional section coverage. Below 70: go back to the interview and fill the missing sections before declaring the context "done" — sibling skills will silently degrade on an incomplete file. Re-run it during the freshness audit too.


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

Proactive Triggers

Surface these without being asked:

  • Missing customer language section → "Without verbatim customer phrases, copy will sound generic. Can you share 3-5 quotes from customers describing their problem?"
  • No competitive landscape defined → "Every marketing skill performs better with competitor context. Who are the top 3 alternatives your customers consider?"
  • Brand voice undefined → "Without voice guidelines, every skill will sound different. Let's define 3-5 adjectives that capture your brand."
  • Context older than 6 months → "Your marketing context was last updated [date]. Positioning may have shifted — review recommended."
  • No proof points → "Marketing without proof points is opinion. What metrics, logos, or testimonials can we reference?"

Output Artifacts

When you ask for...You get...
"Set up marketing context"Guided interview → complete .claude/product-marketing-context.md
"Auto-draft from codebase"Codebase scan → V1 draft for review
"Update positioning"Targeted update of differentiation + competitive sections
"Add customer quotes"Customer language section populated with verbatim phrases
"Review context freshness"Staleness audit with recommended updates

Communication

All output passes quality verification:

  • Self-verify: source attribution, assumption audit, confidence scoring
  • Output format: Bottom Line → What (with confidence) → Why → How to Act
  • Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.

Related Skills

  • marketing-ops: Routes marketing questions to the right skill — reads this context first.
  • copywriting: For landing page and web copy. Reads brand voice + customer language from this context.
  • content-strategy: For planning what content to create. Reads target keywords + personas from this context.
  • marketing-strategy-pmm: For positioning and GTM strategy. Reads competitive landscape from this context.
  • cs-onboard (C-Suite): For company-level context. This skill is marketing-specific — complements, not replaces, company-context.md.
同じリポジトリから

関連する Skills

すべての Skills
alirezarezvani
コミュニティ

content-humanizer

Makes AI-generated content sound genuinely human — not just cleaned up, but alive. Use when content feels robotic, uses too many AI clichés, lacks personality, or reads like it was written by committee. Triggers: 'this sounds like AI', 'make it more human', 'add personality', 'it feels generic', 'sounds robotic', 'fix AI writing', 'inject our voice'. NOT for initial content creation (use content-production). NOT for SEO optimization (use content-production Mode 3).

導入数
2
GitHub Stars
2.9万
更新日
10月23日
alirezarezvani
コミュニティ

analytics-tracking

Set up, audit, and debug analytics tracking implementation — GA4, Google Tag Manager, event taxonomy, conversion tracking, and data quality. Use when building a tracking plan from scratch, auditing existing analytics for gaps or errors, debugging missing events, or setting up GTM. Trigger keywords: GA4 setup, Google Tag Manager, GTM, event tracking, analytics implementation, conversion tracking, tracking plan, event taxonomy, custom dimensions, UTM tracking, analytics audit, missing events, trac

導入数
2
GitHub Stars
2.9万
更新日
10月23日
alirezarezvani
コミュニティ

campaign-analytics

Analyzes campaign performance with multi-touch attribution, funnel conversion analysis, and ROI calculation for marketing optimization. Use when analyzing marketing campaigns, ad performance, attribution models, conversion rates, or calculating marketing ROI, ROAS, CPA, and campaign metrics across channels.

導入数
2
GitHub Stars
2.9万
更新日
10月23日
alirezarezvani
コミュニティ

marketing-demand-acquisition

Creates demand generation campaigns, optimizes paid ad spend across LinkedIn, Google, and Meta, develops SEO strategies, and structures partnership programs. Use when planning demand gen strategy, growth marketing, advertising campaigns, PPC optimization, lead generation, pipeline generation, or marketing budgets. Covers multi-channel acquisition (Google Ads, LinkedIn Ads, Meta Ads), CAC analysis, MQL/SQL workflows, attribution modeling, technical SEO, and co-marketing partnerships. Default cali

導入数
2
GitHub Stars
2.9万
更新日
10月23日