Token导航 LogoToken导航

Agent Skill · 前端设计

value-proposition(价值主张)

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

value-proposition 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 689。

总安装 14,112周安装 588GitHub Stars 10,786下载 4,704核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/phuryn/pm-skills --skill value-proposition

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

value-proposition 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。适用于前端设计类任务,可协助价值主张设计和优化。

通过 npx skills add 命令从 GitHub 安装,需确认权限范围和维护状态。使用前建议检查是否会触发联网、命令执行或文件读写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/value-proposition

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

value-proposition 怎么安装?

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

value-proposition 支持哪些 AI 工具?

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

value-proposition 需要什么权限?

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

value-proposition 是免费的吗?

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

value-proposition 用的人多吗?

公开数据是累计安装 14,112 次,近一周安装 588 次,下载 4,704 次,GitHub 10,786 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

value-proposition 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 来源仓库有 10,786 星,维护活跃度相对可查。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

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

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

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

前端设计类 Skill 对比

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

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
value-proposition

价值主张 · 本页

14,11210,786只读未明确通过

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

SKILL.md 原文

Value Proposition

Metadata

  • Name: value-proposition
  • Description: Generate a detailed value proposition using a 6-part template with JTBD framing. Includes practical examples for designing compelling customer value.
  • Triggers: value proposition, value prop, customer value, JTBD value, value map

Instructions

You are a product strategist designing a clear value proposition for $ARGUMENTS.

Your task is to develop a comprehensive value proposition that articulates the customer value delivered by the product.

Input Requirements

  • Product description and features
  • Target customer segment and their problems
  • Competitive alternatives and current solutions
  • Customer insights or market data

Value Proposition Template

6-Part Structure

1. Who

  • Who is this value proposition for?
  • What customer segment are we addressing?
  • What are their characteristics and constraints?

2. Why (Problem)

  • What is the customer's core problem or need?
  • What's the Job to Be Done (JTBD)?
  • What desired outcomes are they trying to achieve?

3. What Before

  • What is the customer's current situation?
  • What are they using today to solve this problem?
  • What friction or pain exists in the current approach?

4. How (Solution)

  • How does the product solve the problem?
  • What specific features or capabilities deliver value?
  • Why is this solution better than alternatives?

5. What After

  • What is the improved outcome or future state?
  • How does the customer's life/work change?
  • What becomes possible that wasn't before?

6. Alternatives

  • What other solutions could customers use?
  • Why would they choose us instead?
  • What's the switching cost or friction from alternatives?

Example: Canva

  • Who: Non-designers who need to create marketing graphics
  • Why: They need professional-looking designs but can't hire designers or use complex tools
  • What Before: Using PowerPoint, Photoshop (too complex), or hiring expensive designers
  • How: Drag-and-drop templates, built-in design elements, AI design assistance, intuitive interface
  • What After: Create professional designs in minutes, launch campaigns faster, save design costs
  • Alternatives: Photoshop (complex), Fiverr (slow, expensive), Canva competitors (fewer templates, harder UX)

Output Process

  1. Identify and profile the target customer segment
  2. Define the core problem and JTBD
  3. Describe the current state and friction points
  4. Articulate how the product solves the problem
  5. Envision the improved outcome
  6. Compare against competitive alternatives
  7. Create a concise value prop statement (1-2 sentences)
  8. Develop a positioning statement for marketing use

Domain Context

This template vs Strategyzer's Value Proposition Canvas: Strategyzer's canvas (by Alexander Osterwalder) is widely used but has structural limitations. This 6-part JTBD template (by Paweł Huryn and Aatir Abdul Rauf) addresses them:

  • Customer first: This template starts with the customer (Who/Why) and works toward the solution. Strategyzer's canvas places the product on the left, which often leads teams to start with their solution rather than the customer's problem.
  • One segment at a time: This template is designed for one segment per pass. Strategyzer's canvas encourages mapping multiple products/services simultaneously, which dilutes focus.
  • Explicit alternatives: Section 6 (Alternatives) forces you to name what customers would use without you and articulate why you're better. Strategyzer's canvas has no equivalent — you don't directly confront substitutes.
  • Simpler structure: "What before → How → What after" is easier to fill out than separating Customer Jobs, Pains, and Gains on one side and Pain Relievers, Gain Creators, and Products on the other. The separation often creates confusion about where things go.
  • Actionable output: The final Value Proposition Statement is ready for marketing, sales, and onboarding. Strategyzer's canvas doesn't produce a reusable statement.

Use Strategyzer's Value Proposition Canvas when you need a detailed pains/gains decomposition for a mature product with complex customer needs. Use this 6-part template for clarity, speed, and actionable output.

Notes

  • Jobs to Be Done (JTBD) framework focuses on the progress the customer is trying to make, not demographics
  • Value propositions are segment-specific; you may have different value props for different customer groups
  • The stronger your value prop, the easier marketing, sales, and product decisions become
  • Test value props with real customers before finalizing
  • Use a Value Curve (Blue Ocean Strategy) to visually compare your offering against competitors across key factors

Templates


Further Reading

平台分布

Codex

36.42%
按下载量换算1,713

Claude

31.53%
按下载量换算1,483

Cursor

16.76%
按下载量换算788

Gemini CLI

9.94%
按下载量换算468

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills