mcpField
P
price-check

price-check

github.com/anthropicsData & databases33.6k1.4k installsUpdated 1d ago
Repository

About price-check

price-check is a pricing-analysis skill for business owners. It compares current product margins with three pricing scenarios and prepares customer messaging without recommending or changing prices.

Key features

  1. 01QuickBooks revenue and cost analysis
  2. 02PayPal sales cross-validation
  3. 03Three scenario projections
  4. 04Low-margin and incomplete-cost flags
  5. 05Customer messaging brief

Use cases

  1. 01Reviewing margins across active products
  2. 02Comparing price changes against volume shifts
  3. 03Preparing customer communication for a price increase

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/anthropics/knowledge-work-plugins --skill price-check

After installing, type/price-checkin Claude Code to confirm it loaded.

Details

From the project README

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?"

Comments

Markdown supported