Agent skill · data analytics · anthropics
price-check
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. Accepts optional product name argument.
Why this skill is useful
Adds a comprehensive pricing analysis workflow with executable scripts for margin calculations and scenario modeling that aren't in public docs.
What it needs
Requires bash installed locally. Requires paypal, quickbooks account access. About 2k tokens when loaded. Last updated 2026-08-07. 23,345 stars on the source repository.
What this skill does
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: PRODUCTNAME (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: 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills anthropics/price-check