skills/pricing-calculator/SKILL.md
Model pricing scenarios — tiers, margins, break-even, and the revenue impact of a price change. Use when asked to calculate pricing, model a price increase, find break-even volume, set tier prices to a margin target, or estimate the revenue effect of a pricing change. Produces a computed pricing model (per-tier margin, break-even units, price-change revenue impact with an elasticity assumption) and a recommendation.
npx skillsauth add mohitagw15856/pm-claude-skills pricing-calculatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Pricing decisions are usually made on gut and defended with a spreadsheet built under deadline. This
skill does the math cleanly: the margin on each tier, the break-even volume, and the revenue impact of
a price change under an explicit elasticity assumption — so a pricing proposal rests on numbers, with
the assumptions visible. (For the strategy — model, packaging, positioning — pair with
pricing-strategy; this runs the numbers.)
Ask for these only if they aren't already provided:
1. The numbers (via the helper):
| Scenario | Price | Volume | Revenue | Margin | |---|---|---|---|---| | Today | | | | | | Proposed | | | | |
2. The recommendation — what the math supports, and the volume drop you could absorb before the change loses money (the break-even elasticity — the most decision-useful number).
3. Assumptions — elasticity is an estimate; state it, and how sensitive the conclusion is to it.
scripts/pricing.py (stdlib only) runs the margin / break-even / price-change math:
# in.json: {"current_price":50,"variable_cost":10,"current_volume":1000,"price_change_pct":0.2,"volume_change_pct":-0.1,"fixed_costs":20000}
python3 scripts/pricing.py in.json
python3 scripts/pricing.py in.json --json
Pricing & break-even analysis — contribution margin, break-even volume, price-elasticity sensitivity.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.