pricing-value-metric
Choose a Value Metric That Scales
Many B2B companies charge by a unit that does not track customer success, creating margin leakage, gaming, or expansion limits. This skill compares pricing units against four criteria and recommends a defensible hold or metric shift.
使用我的智慧代理安裝
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
Review the Skillstore skill "pricing-value-metric" from https://skillstore.io/skills/cmj-hub-pricing-value-metric.md and its manifest at https://skillstore.io/api/skills/cmj-hub-pricing-value-metric/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
測試它
正在使用「pricing-value-metric」。 We charge per seat, but our customers gain value from automated transactions. Seats remain stable while transaction volume grows.
預期結果:
Recommendation: shift toward a hybrid base plus transaction metric. The current unit misses usage growth and creates expansion limits. Test billing clarity and customer adoption before broad rollout.
正在使用「pricing-value-metric」。 Our per-API-call model is easy to count, but buyers cannot predict monthly bills and frequently limit valuable usage.
預期結果:
Recommendation: evaluate outcome or capped consumption pricing. The current unit creates volume-versus-revenue tension. Confirm outcome attribution and liability boundaries before changing the contract.
正在使用「pricing-value-metric」。 Our per-active-record metric tracks customer scale, has a clear definition, and matches the buyer's reporting language.
預期結果:
Recommendation: hold the metric. Improve tier prices or packaging instead, because all four criteria currently pass.
安全審計
安全All 17 static findings are false positives because the scanned SKILL.md contains pricing documentation, Markdown examples, and reference links rather than executable shell commands or filesystem traversal. No prompt injection or other net-new semantic security finding was identified.
風險因素
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/cmj-hub-pricing-value-metric/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/cmj-hub-pricing-value-metric?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/cmj-hub-pricing-value-metric?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cmj-hub-pricing-value-metric/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/cmj-hub-pricing-value-metric.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>學術引用 (APA · BibTeX · CFF)
APA 引用
cmj-hub. (2026). pricing-value-metric security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cmj-hub-pricing-value-metric/audits/1BibTeX 引用
@techreport{cmj-hub-cmj-hub-pricing-value-metric-2026,
author = {cmj-hub},
title = {pricing-value-metric security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/cmj-hub-pricing-value-metric/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "pricing-value-metric security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "cmj-hub"
date-released: "2026-10-03"
url: "https://skillstore.io/skills/cmj-hub-pricing-value-metric/audits/1"
identifiers:
- type: other
value: "skillstore:cmj-hub-pricing-value-metric:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中你可以打造什麼
Audit a Per-Seat Model
Assess whether seat pricing tracks customer value, usage growth, and expansion potential.
Evaluate Usage Pricing
Compare API calls, transactions, records, or outcomes against buyer language and billing predictability.
Plan a Metric Migration
Select a migration path, estimate directional impact, and define risks before changing the price unit.
試試這些提示
Our current price unit is [unit]. Help me describe what customers pay for and where this metric may misalign with value.
Evaluate [current metric] against success scaling, countability, buyer language, and volume-versus-revenue tension using these facts: [facts].
Compare [current metric] with [candidate metrics] using our customer growth, gaming behavior, billing volatility, and top-to-median billing ratio.
Recommend HOLD or SHIFT for [company]. Include the failing criteria, new metric, expected impact range, risks, migration path, and tribunal test design.
最佳實務
- Provide the top-customer to median billing ratio before evaluating expansion alignment.
- Define the counted unit precisely and document known gaming behaviors.
- Test strategic metric shifts with a controlled migration and customer feedback.
避免
- Do not change the metric because a competitor uses a different unit.
- Do not recommend outcomes without a measurable attribution method.
- Do not treat directional case-study ranges as guaranteed revenue results.