Token导航 LogoToken导航

Agent Skill · 研究检索

pricing-strategy(定价策略)

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

pricing-strategy 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,674 个 Skill 里排第 70,176。

总安装 212周安装 9GitHub Stars 283下载 74核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/mohitagw15856/pm-claude-skills --skill pricing-strategy

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

pricing-strategy 用于查找、检索和筛选相关信息。适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词快速定位候选结果。通过 npx skills add 命令从指定仓库安装并使用该技能。安装前需确认权限范围和维护状态,注意可能触发联网或文件读写操作。

建议结合原始 README 进一步核验具体用法和功能边界。

来源仓库内路径:skills/pricing-strategy

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

pricing-strategy 怎么安装?

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

pricing-strategy 支持哪些 AI 工具?

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

pricing-strategy 需要什么权限?

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

pricing-strategy 是免费的吗?

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

pricing-strategy 用的人多吗?

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

pricing-strategy 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

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

研究检索类 Skill 对比

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

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
pricing-strategy

定价策略 · 本页

212283需要联网未明确通过

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

SKILL.md 原文

Pricing Strategy Skill

Build pricing that reflects value delivered — not cost to build. Structure every pricing decision with customer segmentation, value metric identification, competitive context, and a packaging recommendation.

Pricing Foundations

Three questions to answer before any pricing decision:

  1. Who is our buyer? (Role, company size, willingness to pay)
  2. What value do we deliver? (Quantifiable outcome — time saved, revenue generated, risk reduced)
  3. What is our pricing model? (Per seat, usage-based, flat, hybrid)

Pricing Models

ModelBest ForRisk
Per SeatCollaboration tools, team softwareDisincentivises adoption as team grows
Usage-BasedAPIs, infrastructure, consumption toolsRevenue unpredictability for both sides
Flat RateSimple tools, early-stageLeaves money on table from power users
TieredProducts with clear user segmentsFeature gatekeeping frustrates users
FreemiumViral/PLG products with low marginal costConversion to paid is hard to engineer
Value-BasedEnterprise, outcomes-driven productsRequires strong ROI story

Freemium Decision Framework

Use freemium when:

  • ✅ Marginal cost per free user is near zero
  • ✅ Product is inherently viral (network effects or sharing)
  • ✅ Free tier creates genuine value (not just a demo)
  • ✅ Clear upgrade trigger exists (feature, volume, or team size)
  • ✅ Conversion benchmark is realistic (2–5% free-to-paid is typical)

Avoid freemium when:

  • ❌ Support cost per free user is high
  • ❌ No natural upgrade trigger in the product
  • ❌ Core value requires features you'd need to gate

Packaging / Tiering Framework

Recommended 3-tier structure for SaaS:

TierTargetPrice SignalKey FeaturesLock-in Mechanism
Free / StarterIndividual, early discovery$0Core value, usage-limitedInvite colleagues, export limit
Pro / GrowthSMB, growing teams$[X]/seat/moFull features, higher limitsTeam collaboration, integrations
Business / EnterpriseMid-market, enterprise$[X]/seat/mo or customAdmin, SSO, SLAs, dedicated supportSecurity, compliance, volume

Tier design rules:

  • Each tier should be genuinely sufficient for its target segment
  • The upgrade trigger should be felt naturally — not manufactured
  • Price jumps of 3–5x between tiers are normal and defensible

Competitive Pricing Context

CompetitorModelPriceKey Differentiator
[Name][Model][Price][What they lead with]

Positioning options:

  • Premium: Price 20–40% above market. Justify with enterprise features, support, or brand.
  • Parity: Match the market leader. Win on product or distribution.
  • Value: Price below market. Win on volume. Dangerous without strong unit economics.

Output Format

Pricing Strategy Recommendation — [Product] — [Date]

Current State: [What pricing exists today, if any] Problem to Solve: [Why pricing is being reviewed]

Recommended Pricing Model: [Model name + rationale]

Value Metric: [The single unit that scales with customer value — e.g., "active users", "API calls", "documents processed"]

Proposed Tiers:

[Table using 3-tier structure above]

Free-to-Paid Upgrade Trigger: [Specific moment or threshold that creates natural upgrade pressure]

Competitive Position: [Premium / Parity / Value + reasoning]

Pricing Change Rollout (if applicable):

  • Grandfathering: [Yes / No — recommendation and rationale]
  • Communication plan: [How to tell customers + timing]
  • Rollback plan: [Under what conditions you'd revert]

Risks:

  • [Risk] → Mitigation: [Action]

Metrics to Monitor Post-Change:

  • Conversion rate (free to paid)
  • Churn rate by tier
  • Average revenue per user (ARPU)
  • Expansion revenue

Guidelines

  • Never price based on cost — price based on value delivered to the customer
  • Always A/B test price changes where possible; use geographic holdouts if A/B isn't feasible
  • Recommend annual pricing with 15–20% discount — improves cash flow and reduces churn
  • If enterprise pricing is "contact us", recommend adding a price floor to qualify inbound

平台分布

Codex

36.67%
按下载量换算27

Claude

27.15%
按下载量换算20

Cursor

20.5%
按下载量换算15

Gemini CLI

9.41%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills