agentsclimarketplace

Product pricing

Skill jpoindexter/product-management-skills/skills/product-pricing

Operational product-management skills and a /pm router for Codex and Claude.

Install
npx -y skills add jpoindexter/product-management-skills --skill product-pricing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 15 days oldThe repository was created 15 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Design or critique product pricing, packaging, willingness-to-pay research, and value metrics. Use when the user asks what to charge, how to package capabilities, whether freemium or usage pricing fits, how to test willingness to pay, or how pricing changes product behavior and unit economics.

SKILL.md

2.6 KB, as published. Nobody here has run it

Product Pricing

Treat pricing as a product decision linking customer value, segment, behavior, packaging, economics, and evidence.

Inputs

  • Target segment and buying process
  • Valuable outcome and alternatives
  • Usage pattern and value realization
  • Current price, packaging, and conversion evidence
  • Cost-to-serve and gross-margin constraints
  • Strategic behavior the pricing model should encourage

Workflow

  1. Identify the customer, payer, user, and beneficiary; do not assume they are the same.
  2. Define the valuable outcome and the alternative cost in money, time, risk, or lost opportunity.
  3. Segment by differences in value, need, use, and willingness to pay.
  4. Generate candidate value metrics that grow with customer value, are predictable, measurable, and difficult to game.
  5. Group capabilities into packages with a clear reason for each boundary.
  6. Model unit economics and behavior under realistic low, expected, and high usage.
  7. Design willingness-to-pay research using past purchases, trade-offs, commitments, and live offer tests where appropriate.
  8. Define price-change guardrails, migration treatment, and success criteria.
  9. Recommend a reversible test before an irreversible broad rollout.

Output contract

Return customer and payer roles, value hypothesis, segment differences, candidate value metrics, packaging, price hypotheses, unit-economics sensitivity, research plan, recommendation, risks, and review rule.

Quality gate

  • Price is tied to value and viable economics.
  • Packaging differences are meaningful to a segment.
  • The value metric does not punish desired use.
  • Research asks for trade-offs or commitments, not only acceptable ranges.
  • Existing customers and fairness implications are addressed.

Avoid

  • Cost-plus pricing as the sole method
  • Copying competitor tiers without understanding their strategy
  • Treating stated willingness to pay as purchase behavior
  • Unlimited plans with unbounded variable cost
  • Hiding a weak value proposition behind packaging complexity

Source grounding

Framework-informed operational guidance using evidence principles from The Mom Test, business-model and revenue-stage analysis from Lean Analytics, and positioning context from Obviously Awesome. This first release does not claim source fidelity to Monetizing Innovation.

Gives 0 of the 12 instructions most pricing monetisation skills give

Counted across 366 of the 366 authors here whose files we hold, read 2026-08-06

  • verify webhook signaturesin 23 of 366, across 19 files
  • differentiate tiers using features, limits, or supportin 15 of 366, across 4 files
  • read product marketing context before asking questionsin 14 of 366, across 6 files
  • base price on perceived value, not costin 14 of 366, across 3 files
  • use Van Westendorp to find acceptable price rangein 14 of 366, across 3 files
  • use MaxDiff to identify highly valued featuresin 14 of 366, across 3 files
  • choose a value metric that scales with customer valuein 14 of 366, across 9 files
  • handle webhook events idempotentlyin 12 of 366, across 6 files
  • understand the upgrade context before recommendingin 11 of 366, across 4 files
  • align the pricing metric with delivered valuein 10 of 366, across 4 files
  • install stripe packagein 10 of 366, across 5 files
  • calculate unit economics metricsin 10 of 366, across 5 files

Said here and by no other author read

  • distinguish customer payer user and beneficiary roles
  • define valuable outcome and alternative cost
  • generate candidate value metrics
  • group capabilities into clear packages
  • model unit economics under realistic usage scenarios
  • design willingness-to-pay research using trade-offs and commitments

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.