mcpField
U
usage-based-pricing-review

usage-based-pricing-review

github.com/sylphxaiMarketing & growth150 installsUpdated today
Repository

About usage-based-pricing-review

A skill for analyzing usage-based pricing and producing a pricing architecture, event contract, guardrails, and experiment plan. It guides teams through value metrics, metering, billing states, and customer risk.

Key features

  1. 01Identify buyer, value metric, and cost driver
  2. 02Map metering and billing states
  3. 03Assess predictability, abuse, and growth incentives
  4. 04Produce pricing architecture and experiment plan

Use cases

  1. 01Design a usage-based pricing model
  2. 02Review metering, quotas, alerts, and invoices
  3. 03Plan guardrails for variable usage bills

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill usage-based-pricing-review

After installing, type/usage-based-pricing-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/usage-based-pricing-systems.md

Details

From the project README

Usage Based Pricing Review

Use this skill to turn usage pricing into a trustworthy revenue system instead of a surprise bill generator.

Workflow

  1. Identify buyer, user, value metric, cost driver, usage unit, billing period, and expansion path.
  2. Read references/usage-based-pricing-systems.md.
  3. Map metering, aggregation, quota, alert, invoice, adjustment, dispute, and support states.
  4. Separate customer value, provider cost, predictability, abuse risk, and growth incentives.
  5. Produce pricing architecture, event contract, guardrails, and experiment plan.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not hide metering logic, renewal price, overage rules, or invoice timing.
  • Do not choose a metric solely because it is easy to meter; it must correlate with customer value.
  • Provide budgets, caps, alerts, and support evidence before exposing high-variance bills.

Output format

Pricing context:
Recommended value metric:

Usage system:
- meter, unit, aggregation, allowance, overage, cap, alert

Plan architecture:
- free/trial:
- core paid:
- expansion:
- enterprise/control:

Risks and mitigations:
- <risk> -> product, billing, support, analytics response

Instrumentation:
- <event> with properties

Comments

Markdown supported