Price check

Skill nota-america/forgecat-agent-profiles/profiles/forgecat/forgecat-agent-profiles/small-business-agent-team/for-forgecat/skills/price-check

Production-ready AI agent profiles for Claude Code, Cursor, and Codex. Search, install, and contribute ForgeCat packages.

Install

npx -y skills add nota-america/forgecat-agent-profiles --skill price-check

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

One thing to look at

24 stars24 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

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.

SKILL.md

2.9 KB, 600 tokens by cl100k_base, as published. Nobody here has run it

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:

Pull QuickBooks revenue by product/service for the last 90 days.
Pull COGS or direct costs per product from QuickBooks (if categorized).
Pull PayPal gross sales for the same products to cross-validate.
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?"