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.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
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.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "pricing-value-metric". We charge per seat, but our customers gain value from automated transactions. Seats remain stable while transaction volume grows.
Expected outcome:
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.
Using "pricing-value-metric". Our per-API-call model is easy to count, but buyers cannot predict monthly bills and frequently limit valuable usage.
Expected outcome:
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.
Using "pricing-value-metric". Our per-active-record metric tracks customer scale, has a clear definition, and matches the buyer's reporting language.
Expected outcome:
Recommendation: hold the metric. Improve tier prices or packaging instead, because all four criteria currently pass.
Security Audit
SafeAll 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.
Risk Factors
⚙️ External commands (12)
📁 Filesystem access (3)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/cmj-hub-pricing-value-metric/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/cmj-hub-pricing-value-metric?utm_source=security_passport_badge)HTML badge
<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>Embed card
<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>Academic citations (APA · BibTeX · CFF)
APA citation
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 citation
@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 Score
Why this score Evidence Confidence: MediumWhat You Can Build
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.
Try These Prompts
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.
Best Practices
- 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.
Avoid
- 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.