Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计提醒

product-marketing-context产品营销背景

Agent Skill

product-marketing-context 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

190

周安装

8

GitHub Stars

4

下载量

67
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:product-marketing-context(产品营销背景)
来源仓库:https://github.com/insight68/skills
仓库路径:skills/product-marketing-context
安装命令:
npx skills add https://github.com/insight68/skills --skill product-marketing-context
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/insight68/skills --skill product-marketing-context

简介

product-marketing-context 用于查找、检索和筛选相关信息,适合在产品营销背景分析中快速定位内容。

  • 它支持根据关键词和任务场景组织信息,适用于市场策略与产品定位研究。
  • 可通过 npx skills add 命令从指定仓库安装并使用该技能。
  • 安装前需确认权限范围和维护状态,避免触发不必要的联网或文件操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

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 .claude/product-marketing-context.md.

Workflow

Step 1: Check for Existing Context

First, check if .claude/product-marketing-context.md already exists.

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

Important: Push for verbatim customer language. Exact phrases are more valuable than polished descriptions.


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 .claude/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 .claude/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)

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.16%
按下载量换算23

Claude

28.51%
按下载量换算19

Cursor

18.75%
按下载量换算13

Gemini CLI

9.43%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills