Token导航 LogoToken导航

Agent Skill · 待分类

pricing-strategist(定价策略师)

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

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

总安装 4,460周安装 184GitHub Stars 141下载 1,457核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/ognjengt/founder-skills --skill pricing-strategist

这个 Skill 是做什么的

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

用于处理 GitHub 仓库、Issue 和 Pull Request 信息。适合围绕代码变更或协作事项进行整理。可结合来源仓库 README 继续核验具体用法。安装前建议确认权限范围、维护状态及是否会触发联网或文件操作。pricing-strategist 属于待分类类 Skill,可作为该场景下的辅助能力补充。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

pricing-strategist 怎么安装?

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

pricing-strategist 支持哪些 AI 工具?

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

pricing-strategist 需要什么权限?

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

pricing-strategist 是免费的吗?

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

pricing-strategist 用的人多吗?

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

pricing-strategist 安全吗?

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

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

值得选的地方

  • 同时适配 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操作浏览器未明确未通过
pricing-strategist

定价策略师 · 本页

4,460141需要联网未明确通过

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

SKILL.md 原文

Pricing Strategist

Purpose

Build a comprehensive, justified pricing strategy — tier structures, price points, positioning, and revenue optimization — tailored to the business through context and conversation.


Execution Logic

Check $ARGUMENTS first to determine execution mode:

If $ARGUMENTS is empty or not provided:

Respond with: "pricing-strategist loaded, ready to build your pricing strategy"

Then wait for the user to provide context in the next message.

If $ARGUMENTS contains content:

Proceed immediately to Task Execution (skip the "loaded" message).


Task Execution

1. MANDATORY: Read FOUNDER_CONTEXT.md

BLOCKING REQUIREMENT — DO NOT SKIP THIS STEP

Before doing ANYTHING else, read FOUNDER_CONTEXT.md from the project root. Extract everything relevant to pricing:

  • Company name, industry, product/service type
  • Target audience (demographics, pain points, budget signals)
  • Existing pricing model (if any)
  • Competitors and their pricing (if mentioned)
  • Value proposition and key features/benefits
  • Business stage and revenue goals

DO NOT PROCEED to Step 2 until this file has been read.

2. Determine Which Questions to Ask

Cross-reference what FOUNDER_CONTEXT.md already provides against the Question Bank below. Only ask questions where the answer is genuinely missing or unclear. Never ask something the context already answers.

Question Bank (priority order):

#QuestionWhy it mattersSkip if...
1B2B or B2C?Changes deal size, tier logic, sales cycle, everythingTarget audience section makes it obvious
2What pricing model do you prefer or want to avoid? (subscription, one-time, usage-based, freemium, hybrid)Determines the entire structurePricing model already stated in context
3What's the primary value metric that scales with usage? (seats, API calls, storage, projects, transactions, etc.)Drives tier differentiation and upgrade logicProduct type + features make it obvious
4Target gross margin range? (60-70%, 70-80%, 80%+, not sure)Sets the floor for every price pointA number or range is already given
5How price-sensitive is your target customer? (very sensitive, moderate, willing to pay premium)Calibrates price positioning and tier gapsAudience detail + industry norms make it clear
6Who are your closest competitors and how do they price?Market anchoring — prevents under or over pricingCompetitors section is filled
7What's your current stage or revenue target? (pre-revenue, <$10K MRR, $10-50K MRR, $50K+ MRR)Calibrates ambition and tier complexityBusiness goals mention revenue or stage

Use AskUserQuestion to ask up to 4 questions per batch. Ask the highest-priority unanswered questions first. If the first batch gives you enough to build a confident strategy, stop. Maximum 7 questions total, but fewer is better — stop as soon as you can build a strong strategy with what you have.

3. Determine Strategy Type

Based on all collected inputs, decide the structure. Make this decision yourself — do not ask the user. Explain why in the output.

ConditionStrategy Type
Subscription + B2BSaaS Tiered — Starter / Pro / Business / Enterprise
Subscription + B2CConsumer Tiered — Free / Basic / Premium
Usage-based primaryUsage Tiers — base fee + usage bands with overage pricing
One-time purchasePackage Pricing — Good / Better / Best bundles
Freemium preferredFreemium — generous free tier + 2-3 paid tiers
Mixed signalsHybrid — combine structures as the inputs warrant

4. Build the Pricing Strategy

For each tier, define:

  • Plan name — descriptive, not generic. "Starter" beats "Plan A". "Growth" beats "Mid".
  • Price point — monthly AND annual (annual ≈ 20% off monthly). Use specific numbers.
  • Price justification — why this number. Anchor to: competitor benchmarks, value delivered, margin targets, or customer willingness to pay. Never leave a price unjustified.
  • Feature set — what's in, and critically, what's deliberately left out to drive upgrades.
  • Target segment — the specific customer who buys this tier and why.

5. Add the Strategic Layer

Beyond the tiers:

  • Positioning — where this sits vs. competitors (premium, mid-market, value leader, underdog)
  • Psychological tactics used — name them and explain why each one was chosen (charm pricing, anchoring, decoy effect, loss aversion in annual vs. monthly, etc.)
  • Upgrade triggers — what specifically moves a customer from tier N to tier N+1
  • Revenue optimization — annual discount incentives, add-ons, usage overages, upsell moments
  • Biggest pricing risk — one specific risk for this business and how to mitigate it

6. Format and Verify

  • Structure output per Output Format below
  • Run through Quality Checklist before presenting

Pricing Principles

Hard constraints. These exist because bad pricing destroys margins or kills growth.

  • Price on value delivered. Never on cost to build.
  • Every tier must have a clear reason to exist. If no real customer would buy it, cut it.
  • The middle tier is the hero. Design the strategy so most customers land there.
  • Annual pricing should feel like a no-brainer — 20-25% off. Monthly is the convenience premium.
  • Never show more than 4 tiers. Paradox of choice kills conversion at the pricing page.
  • Enterprise = "contact sales" unless the business is pre-revenue. Pre-revenue can skip Enterprise or price it transparently.
  • Freemium only works if the free tier is genuinely useful AND the paid upgrade is obviously better. A crippled free tier is worse than no free tier.
  • Specific numbers build credibility: $47/mo reads more trustworthy than $50/mo. Use this deliberately — not on every price point, but on the hero tier.
  • B2B + deal size above $200/mo → seat-based pricing is almost always correct.
  • B2C + habit-forming product → monthly subscription is the priority structure. Annual is secondary.
  • Price anchoring matters. The highest tier primes the customer to see the middle tier as reasonable. Design for that.

Output Format

## Pricing Strategy for [Company Name]

**Strategy type:** [SaaS Tiered / Consumer Tiered / Usage Tiers / Package / Freemium / Hybrid]
**Why this structure:** [2-3 sentences. Why this model, not another.]

---

### [Tier 1 Name]
- **Price:** $X/mo | $Y/yr (save Z%)
- **Who it's for:** [Specific customer segment — not "small businesses"]
- **What's included:** [Concrete feature list]
- **Price justification:** [Why this number. Anchored to what.]

### [Tier 2 Name]
- **Price:** $X/mo | $Y/yr (save Z%)
- **Who it's for:** [Specific segment]
- **What's included:** [Feature list — highlight what's new vs. Tier 1]
- **Price justification:** [Why this number]

### [Tier 3 Name]
[same structure]

---

### Positioning & Psychology
- **Market position:** [Where you sit vs. named competitors]
- **Psychological tactics:** [List each one used and the specific reason]
- **Upgrade triggers:** [What moves customers between tiers — specific, behavioral]

### Revenue Optimization
- [Specific recommendation 1]
- [Specific recommendation 2]
- [Specific recommendation 3]

### Biggest Pricing Risk
[One specific risk for this business. Not generic. How to see it coming and what to do.]

Quality Checklist (Self-Verification)

Pre-Execution Check

  • I read FOUNDER_CONTEXT.md before asking any questions
  • I only asked questions the context didn't already answer
  • Total questions asked: 7 or fewer

Strategy Check

  • Strategy type is justified (not a generic default)
  • Each tier has a clear reason to exist
  • Middle tier is the obvious "best value" — the hero
  • Price points are anchored to competitors, value, or willingness to pay — not guessed
  • Annual pricing is 20-25% below monthly
  • 4 tiers or fewer

Pricing Principles Compliance

  • All prices are value-based
  • Freemium tier (if present) is genuinely useful, not crippled
  • B2B high-value products use seat-based logic where appropriate
  • Psychological tactics are named and justified

Output Check

  • Every tier has a price justification — none are bare numbers
  • Positioning is specific to this business and its competitors
  • Revenue optimization is actionable, not generic
  • The "biggest risk" is specific to this business — not boilerplate

If ANY check fails → revise before presenting.


Defaults & Assumptions

Use these unless the user overrides:

  • Pricing model: Subscription (most common for modern products)
  • Tiers: 3 for most businesses. 4 only if B2B with a clear Enterprise segment.
  • Annual discount: 20%
  • Target gross margin: 75-80% (SaaS baseline; adjust for non-software)
  • Price sensitivity: Moderate (mid-market default)
  • Currency: USD
  • Billing cycle: Monthly with annual option

Document any assumptions made in the output.

平台分布

Codex

35.22%
按下载量换算513

Claude

31.94%
按下载量换算465

Cursor

18.98%
按下载量换算277

Gemini CLI

8.69%
按下载量换算127

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills