
Price Check
- 1k installs
- 23.3k repo stars
- Updated August 5, 2026
- anthropics/knowledge-work-plugins
Price-check is a Claude skill that builds a margin-by-product table and three pricing-scenario data views so an owner can decide what to charge.
About
Price-check produces a margin-by-product table and three pricing-scenario data views so an owner can see the full financial picture before setting a price. It pulls QuickBooks revenue and COGS, cross-validates against PayPal, and models hold, increase, and decrease scenarios with break-even volumes. It presents data only and never recommends or updates a price, and for increase scenarios it adds a customer messaging brief.
- Builds a margin-by-product table from QuickBooks revenue and COGS cross-validated against PayPal
- Models three pricing scenarios (hold, increase, decrease) with break-even volume math
- Produces a customer messaging brief for price increases; never recommends a price
Price Check by the numbers
- 1,011 all-time installs (skills.sh)
- +85 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #149 of 1,106 Finance & Trading skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
price-check capabilities & compatibility
- Capabilities
- margin analyzer · sales brief
- Use cases
- data analysis · copywriting
What price-check says it does
Produces a margin-by-product table and three pricing-scenario data views so the owner can see the full financial picture before making a pricing decision.
Never recommend a specific price.** Provide data views only — pricing decisions belong to the owner.
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill price-checkAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1k |
|---|---|
| repo stars | ★ 23.3k |
| Last updated | August 5, 2026 |
| Repository | anthropics/knowledge-work-plugins ↗ |
What it does
Build a margin-by-product table and three pricing scenarios so an owner can decide what to charge.
Who is it for?
Owners weighing a price change who want margin and scenario math first.
Skip if: Owners who want the tool to pick or update a price for them.
When should I use this skill?
The user asks about margins, whether to raise prices, cost per unit, or what to charge.
What you get
A margin-by-product table plus hold/increase/decrease scenario tables and, for increases, a customer messaging brief.
- margin-by-product table
- three pricing scenario tables
- customer messaging brief
By the numbers
- three pricing scenarios
- flags margin below 20%
- last 90 days of revenue
Files
Run the pricing analysis. Pull cost and revenue data, build the margin table, and model three pricing scenarios — so the owner can see the numbers clearly before deciding what to charge.
Parse arguments:
PRODUCT_NAME(optional) — specific product or service to analyze; if omitted, analyze all active products
Step 1 — Current margin baseline
Using the margin-analyzer skill workflow:
1. Pull QuickBooks revenue by product/service for the last 90 days. 2. Pull COGS or direct costs per product from QuickBooks (if categorized). 3. Pull PayPal gross sales for the same products to cross-validate. 4. Calculate current gross margin per product: (revenue − COGS) ÷ revenue.
Build the margin table:
Product | Revenue | COGS | Gross Margin | Margin %
{product} | ${amt} | ${amt} | ${amt} | {X}%Flag any product with margin below 20% as a risk.
Step 2 — Three pricing scenarios
For each product (or the specified product), model three scenarios. Do NOT recommend a price — present data only.
Scenario A — Hold current price
- Project revenue at current price × current volume
- Project margin at current COGS
Scenario B — Price increase (+10% to +20%, owner to specify)
- Project revenue assuming 0%, 5%, and 10% volume loss at new price
- Show the break-even volume needed to maintain current profit
Scenario C — Price decrease (−10%, to drive volume)
- Project revenue assuming 10%, 20%, and 30% volume increase
- Show the volume needed to match current profit
Present each scenario as a data table, not a recommendation.
Step 3 — Customer messaging brief
Produce a plain-language brief (for price increase scenarios) the owner can use to communicate a change to customers:
- One paragraph explaining the change
- Three key message options (direct, value-focused, empathetic)
- Suggested timing and channel (email, invoice note, in-person)
Connector failures
If QuickBooks is unreachable, stop — margin analysis requires QB revenue and cost data. If PayPal is missing, run from QB-only and note "PayPal not connected — cross-validation against PayPal sales skipped."
Approval gates
- Never recommend a specific price. Provide data views only — pricing decisions belong to the owner.
- Flag if COGS data is incomplete (many QB setups don't track per-product COGS) and note the gap.
- Never update any prices in QB, PayPal, or any connected system.
Output
Present the margin table, then the three scenario tables side-by-side. If a price increase scenario is being considered, append the customer messaging brief. End with: "Which scenario would you like to explore further?"
Related skills
FAQ
Will price-check recommend a price?
No. It presents the margin table and scenario tables as data only; the pricing decision belongs to the owner.
What scenarios does it model?
Hold current price, a price increase (+10 to +20%) with volume-loss cases, and a price decrease (−10%) with volume-increase cases, plus break-even volumes.