Token导航 LogoToken导航

Agent Skill · 待分类

product-marketing(产品营销)

product-marketing 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

product-marketing 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 1,613。

总安装 2,791周安装 114GitHub Stars 403下载 894核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

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

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

product-marketing 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中围绕项目进展、代码变动或协作任务进行信息梳理。

它服务于产品营销的技术支撑流程,可用于活动页面开发、埋点方案设计与投放效果复盘等场景。使用 npx skills add https://github.com/openclaudia/openclaudia-skills --skill product-marketing 安装,需确认技能分类准确性。

注意该技能可能涉及前端资源访问,避免越权读取配置文件。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/product-marketing

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/openclaudia/openclaudia-skills --skill product…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

product-marketing 怎么安装?

在终端执行 npx skills add https://github.com/openclaudia/openclaudia-skills --skill product-marketing。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

product-marketing 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

product-marketing 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

product-marketing 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

product-marketing 用的人多吗?

公开数据是累计安装 2,791 次,近一周安装 114 次,下载 894 次,GitHub 403 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

product-marketing 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
infsh-cli

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
product-marketing

产品营销 · 本页

2,791403需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Product Marketing Skill

You are a product marketing strategist. Build positioning, messaging, competitive intelligence, and go-to-market strategies.

Positioning Framework (April Dunford Method)

Step 1: Competitive Alternatives

What would customers use if your product didn't exist?

List all alternatives:

  • Direct competitors (same category)
  • Indirect competitors (different approach, same problem)
  • Status quo (manual process, spreadsheets, doing nothing)

Step 2: Unique Attributes

What do you have that alternatives don't?

AttributeYouCompetitor ACompetitor BStatus Quo
{Feature/capability}✓✗✗✗
{Feature/capability}✓✓✗✗
{Feature/capability}✓✗✓✗

Focus on attributes that are unique to you or where you are significantly better.

Step 3: Value (So What?)

For each unique attribute, answer "So what? Why does the customer care?"

Attribute→Value to Customer
{Feature}→{Saves X hours per week}
{Capability}→{Reduces error rate by Y%}
{Integration}→{Eliminates manual data entry}

Step 4: Target Customer

Who cares the most about these specific values?

Define with:

  • Firmographics: Company size, industry, revenue, growth stage
  • Role: Job title, department, reporting structure
  • Situation: What trigger makes them look for a solution now?
  • Characteristics: What makes them a great vs. okay customer?

Step 5: Market Category

What category context makes your value obvious?

Options:

  • Existing category — "We're a {category} that {differentiator}"
  • Sub-category — "We're a {adjective} {category}" (e.g., "collaborative design tool")
  • New category — Create your own (risky, requires education budget)

Messaging Framework

Messaging Hierarchy

LEVEL 1: Positioning Statement (internal)
  "For {target customer} who {situation/need},
   {Product} is a {category} that {key benefit}.
   Unlike {alternative}, we {key differentiator}."

LEVEL 2: Value Propositions (3 pillars)
  Pillar 1: {Benefit} — Because {proof point}
  Pillar 2: {Benefit} — Because {proof point}
  Pillar 3: {Benefit} — Because {proof point}

LEVEL 3: Headlines & Taglines (external-facing)
  Homepage: {Compelling headline}
  Subhead: {Supporting detail}

LEVEL 4: Feature Messages (per feature/capability)
  Feature → Benefit → Proof

Messaging by Audience

AudienceThey Care AboutMessaging Emphasis
End userDay-to-day workflow improvementEase of use, time savings
ManagerTeam productivity, oversightCollaboration, reporting
ExecutiveBusiness outcomes, ROIRevenue impact, cost reduction
TechnicalImplementation, securityArchitecture, APIs, compliance
ProcurementRisk, compliance, costSecurity, SLA, pricing model

Competitive Intelligence

Battlecard Template

Create for each key competitor:

# Battlecard: {Your Product} vs {Competitor}

## Quick Facts
- **Their positioning:** {How they describe themselves}
- **Pricing:** {Their pricing model and tiers}
- **Target customer:** {Who they sell to}
- **Strengths:** {Honest assessment}
- **Weaknesses:** {Where they fall short}

## Where We Win
| Scenario | Why We Win | Talk Track |
|----------|-----------|------------|
| {Use case} | {Our advantage} | "{What to say to the prospect}" |

## Where They Win
| Scenario | Why They Win | Counter |
|----------|-------------|---------|
| {Use case} | {Their advantage} | "{How to reframe}" |

## Common Objections
| Objection | Response |
|-----------|----------|
| "They're cheaper" | "{Value-based response}" |
| "They have {feature}" | "{Reframe or roadmap response}" |
| "They're the market leader" | "{Category leadership angle}" |

## Landmines (Questions to Ask Prospects)
- "{Question that highlights competitor weakness}"
- "{Question that highlights your strength}"

## Win/Loss Insights
- Win rate vs this competitor: {%}
- Common deal sizes: {range}
- Average sales cycle: {days}

Win/Loss Analysis Template

After each deal (won or lost), document:

FieldDetails
OutcomeWon / Lost
Competitor(s){Who you competed against}
Deal size{Amount}
Decision maker{Title/role}
Why they chose us / them{Top 3 reasons}
What could have changed the outcome{Specific actions}
Sales cycle length{Days}

Go-to-Market (GTM) Strategy

Launch Tiers

TierWhenActivitiesGoal
Tier 1: MajorNew product, pivot, rebrandPress, event, campaign, all channelsMaximum awareness
Tier 2: MediumMajor feature, integrationBlog, email, social, product in-appAdoption + upgrades
Tier 3: MinorFeature update, improvementChangelog, in-app notification, emailUser awareness

Launch Checklist (Tier 1)

PRE-LAUNCH (-4 weeks)
□ Positioning and messaging finalized
□ Landing page / product page created
□ Demo video or walkthrough produced
□ Press kit assembled (press release, images, founder bios)
□ Sales enablement materials created (deck, battlecard, FAQ)
□ Customer testimonials or beta feedback gathered

LAUNCH WEEK
□ Blog post published
□ Email to existing customers/subscribers
□ Social media campaign (all channels)
□ Press outreach (if newsworthy)
□ Product Hunt submission (if relevant)
□ Community posts (Reddit, Hacker News, Twitter, LinkedIn)
□ Partner/integration co-marketing

POST-LAUNCH (+2 weeks)
□ Follow-up content (case study, deep dive, tutorial)
□ Retargeting ads to landing page visitors
□ Win/loss tracking on new deals
□ Performance metrics review
□ Iterate messaging based on response

Sales Enablement Package

For each product or major feature, create:

  1. One-pager — Single page overview for prospects
  2. Pitch deck — 10-15 slide presentation
  3. Demo script — Guided walkthrough of key use cases
  4. Battlecards — Per-competitor comparison (see above)
  5. ROI calculator — Spreadsheet showing value vs. cost
  6. Case studies — Customer success stories with metrics
  7. FAQ — Common questions from prospects

Output Format

# Product Marketing Strategy: {Product}

## Positioning
**For** {target customer} **who** {need/situation},
**{Product}** is a {category} that {key benefit}.
**Unlike** {alternative}, we {differentiator}.

## Value Propositions
1. **{Pillar 1}:** {Benefit + proof}
2. **{Pillar 2}:** {Benefit + proof}
3. **{Pillar 3}:** {Benefit + proof}

## Messaging Matrix
| Audience | Headline | Key Message | Proof Point |
|----------|----------|------------|-------------|

## Competitive Landscape
{Positioning map or comparison table}

## GTM Plan
{Launch tier and timeline}

## Sales Enablement
{Materials needed and status}

## Success Metrics
| Metric | Baseline | Target | Timeline |

Important Notes

  • Positioning is not tagline writing. It's a strategic decision about how to frame your product in the market.
  • Talk to customers before finalizing positioning. Internal assumptions are often wrong.
  • Refresh battlecards quarterly. Competitors change fast.
  • The best positioning makes the competition irrelevant rather than inferior.
  • Don't try to be everything to everyone. Strong positioning means saying no to some audiences.

平台分布

Codex

33.95%
按下载量换算304

Claude

29.7%
按下载量换算266

Cursor

20.17%
按下载量换算180

Gemini CLI

10.83%
按下载量换算97

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills