Token导航 LogoToken导航

Agent Skill · 开发

pricing(pricing 开发)

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

pricing 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 20,160。

总安装 238周安装 10GitHub Stars 168下载 83核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/whawkinsiv/claude-code-skills --skill pricing

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

pricing 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合在定价策略开发与协作流程中提供支持。可通过 npx skills add 命令从 GitHub 仓库安装。安装前建议检查其访问权限及对系统的影响范围。

pricing 属于开发类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/pricing

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

pricing 怎么安装?

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

pricing 支持哪些 AI 工具?

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

pricing 需要什么权限?

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

pricing 是免费的吗?

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

pricing 用的人多吗?

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

pricing 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

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

开发类 Skill 对比

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

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
pricing

pricing 开发 · 本页

238168需要联网未明确通过

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

SKILL.md 原文

Pricing & Monetization

Price is a signal. Too low says "toy." Too high says "enterprise." Your price tells customers who this product is for. This skill helps you choose what to charge, how to structure tiers, and how to build a pricing page that converts.

Core Principles

  • Pricing is a psychology problem, not a math problem.
  • Align price with the value metric — the unit of value your customer receives.
  • Three tiers is the default for a reason: anchoring, self-selection, and upgrade paths.
  • The best pricing is simple to understand and hard to outgrow.
  • Most SaaS companies underprice by 2-3x. Revisit pricing every 6 months.

Workflow

Pricing Setup:
- [ ] Choose your value metric
- [ ] Design tier structure (Free → Pro → Business)
- [ ] Set price points
- [ ] Build the pricing page
- [ ] Plan expansion revenue mechanics

Step 1: Choose Your Value Metric

The value metric is what you charge for. It should be:

  1. Easy to understand: The customer can predict their bill.
  2. Aligned with value: As they get more value, they pay more.
  3. Scalable: It grows with their usage naturally.
SaaS TypeGood Value Metric
Collaboration toolsPer seat/user
Developer toolsAPI calls, compute time, builds
Marketing toolsContacts, emails sent, campaigns
AnalyticsEvents tracked, data points, queries
Storage/infraGB stored, bandwidth

Bad value metrics: Features-only gating (bloated top tiers), flat pricing (no expansion revenue), complex formulas nobody can predict.

Tell AI:

Help me choose a value metric for my SaaS:
- Product: [what it does]
- Users: [who uses it and how]
- Core value: [what outcome users get]
- Current model: [if any — flat rate, per user, etc.]

Recommend a value metric that's easy for users to understand, scales with the value
they receive, and creates natural expansion revenue. Show 2-3 options with tradeoffs.

Step 2: Design Tier Structure

Free / Starter:

  • Purpose: Acquisition. Get users in the door.
  • Include: Core value prop, limited quantity (not crippled features).
  • Limit: 1 user, 3 projects, 1,000 events, etc.
  • Avoid: Time-limited free tiers for bottom-up SaaS. Use quantity limits.

Pro / Team:

  • Purpose: Conversion. This is your primary revenue tier.
  • Include: Everything in Free + collaboration + higher limits + integrations.
  • Price: $10-30/user/month for SMB, $30-80 for mid-market.
  • This tier should feel like an obvious upgrade when they hit Free limits.

Business / Scale:

  • Purpose: Expansion. Capture more value from power users.
  • Include: Everything in Pro + advanced features (SSO, audit logs, API access, priority support).
  • Price: 2-3x the Pro tier.

Enterprise (optional for now):

  • Purpose: Large deals. Custom pricing = "Contact us."
  • Gate: SSO, SAML, SCIM, advanced security, SLA.

Tell AI:

Design pricing tiers for my SaaS:
- Product: [what it does]
- Value metric: [what you're charging for — users, projects, events, etc.]
- Target customer: [SMB, mid-market, enterprise]
- Competitors charge: [list 2-3 competitor prices if known]

Create 3 tiers with:
- Tier name, price, and what's included
- Clear differentiation between tiers (not just "more of the same")
- A reason to upgrade at each level (hit a limit, need a feature)
- The specific limits for the free tier

Step 3: Set Price Points

Psychological Pricing Tactics

  • Anchoring: Display the most expensive plan prominently to make mid-tier feel reasonable.
  • Decoy effect: Make the middle tier clearly the best value relative to the others.
  • Charm pricing: $29 vs $30 — the effect is real, especially for SMB.
  • Per-day framing: "Less than $1/day" for higher-priced plans.
  • Loss aversion: On trial expiry, emphasize what they'll lose, not what they'll gain.

Freemium vs. Free Trial

Choose Freemium when:

  • Your product has viral/network effects (users invite others)
  • The free tier drives organic growth or word-of-mouth
  • Your marginal cost per free user is very low
  • You're selling bottom-up (PLG)

Choose Free Trial when:

  • The product's value requires setup/investment to experience
  • You sell to decision-makers who evaluate then buy
  • You can't afford to support large numbers of free users

Reverse Trial (best of both): Give FULL access for 14 days, then downgrade to free tier. Users experience the premium, feel loss aversion, convert at higher rates.


Industry Pricing Anchors

If you're building for your own profession, you already know what your peers pay for tools. Use this knowledge.

Tell AI:

Help me set pricing for my SaaS. Context about my industry:
- My target users are [profession/role]
- They currently pay for these tools: [list tools and rough prices]
- Their typical budget for software: [$ range per month, or "they expense it"]
- Buying decision made by: [individual practitioner / office manager / firm partner]
- Price sensitivity: [very price-sensitive / moderate / "if it works, cost doesn't matter"]

Based on these industry anchors, what price range makes sense?
Position my product relative to what they already pay.

Key insight: Your peers' existing software spending sets the anchor, not your costs. If every dentist already pays $300/month for practice management software, a $49/month add-on feels trivial. If your audience pays $0/month for tools, $29/month feels like a big ask.


Step 4: Build the Pricing Page

Tell AI:

Build a pricing page for our SaaS:
- Tiers: [paste your tier structure from Step 2]
- Default to annual billing (show monthly as toggle)
- Show savings: "Save 20% with annual billing"
- Highlight the recommended plan with a "Most Popular" badge
- Feature comparison table below the tier cards
- FAQ section answering: "Can I cancel anytime?", "What happens to my data?",
  "Is there a setup fee?", "Can I switch plans?"
- Add social proof near the CTA: "[X] teams already use [Product]"
- Add a "Not sure?" CTA linking to a contact form or quiz

Use the design patterns from our existing pages. Make it responsive.

Step 5: Plan Expansion Revenue

Don't just set it and forget it. Design mechanics that grow revenue as users grow.

  • Usage-based overages: Charge for going over limits rather than hard-blocking.
  • Seat expansion: Make it easy to add seats with self-serve billing.
  • Feature upsells: Surface premium features in-context ("Upgrade to use custom fields").
  • Upsell timing: Trigger when users hit 80% of a limit, not 100%.

Tell AI:

Add upgrade prompts to our product:
- When users hit 80% of their [resource] limit, show a gentle banner:
  "You're using 8 of 10 [resources]. Upgrade for unlimited."
- When users try a gated feature, show a modal explaining the feature
  and which plan includes it
- On the dashboard, show a usage meter: "X of Y [resource] used"
- Make the upgrade flow self-serve (no "contact sales" for Pro tier)

Testing Price Changes

If you already have customers and want to adjust pricing:

  • Grandfather existing customers at the old price (at least for 6-12 months)
  • Test on new signups only — never change pricing mid-contract without notice
  • A/B test the page, not the price — test how you present pricing, not different prices for the same plan
  • Announce increases 30+ days in advance with clear reasoning

Common Mistakes

MistakeFix
Pricing based on costs, not valuePrice based on what the customer saves or earns, not what it costs you
Only one paid tierThree tiers enable anchoring and self-selection
Free tier is too generousFree should create desire to upgrade, not satisfy forever
No annual discountAnnual billing improves cash flow and reduces churn
Hiding pricing ("Contact us" at $20/mo)Show prices for SMB plans. Only hide enterprise/custom
Never revisiting pricingReview every 6 months. You're probably underpricing.

Related Skills

  • conversion — Optimize the pricing page for higher conversion
  • payments — Implement Stripe, subscriptions, and billing
  • landing-page — Build the full marketing site around pricing
  • analytics — Track pricing page views, plan selection, and upgrade triggers

平台分布

Codex

35.36%
按下载量换算29

Claude

28.08%
按下载量换算23

Cursor

17.96%
按下载量换算15

Gemini CLI

8.65%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills