When should you use it?
- Your estimator is the bottleneck and quotes wait days for pricing
- A manager asks where a price came from and nobody can rebuild it quickly
- Customers counter on price and you lose track of which version they saw
Not for: Catalog or fixed-price products that never need a fresh cost buildup; Shops with no recorded labor, burden or margin rates; it will price only what it can trace; Sending quotes automatically; a person releases every version
What do you need, and what do you get?
You need
- The intake form or RFQ details, with quantities, materials and drawing revision
- Cost history: past work orders, recent purchase orders and standard costs, from your ERP or exports
- Labor, burden and margin rates recorded during plugin setup
- A planning export of current shop load, if you want the date checked
You get
- A customer quote with prices per quantity break, lead time, terms and listed assumptions
- An internal cost sheet citing the source of every cost, the comparable jobs and the margin
- A list of lines it could not price and the missing input behind each
- A date check against shop load, or a clear note that it was not checked
- A revision record when the customer counters
How does it work, step by step?
- Install and onboardAdd Claude for Manufacturing from the Claude plugin directory and record your labor, burden and margin rates during setup.
- Connect the cost historyConnect your ERP or attach exports of closed work orders, purchase orders and the planning schedule.
- Ask for the quoteSay 'build the quote' with the intake form or RFQ attached.
- Review both documentsCheck the internal sheet for blocked lines, capability flags and the date check, then read the customer version on its own.
- Release and reviseSend the quote yourself. When the customer pushes back, ask for a revision so the change record stays with the original.
The prompt
Our adapted version, written to work in Claude, Claude Cowork and Claude Code. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Build a quote for {customer} for {part} at quantities {quantities}, using {intake_form} and our cost history in {cost_sources}. Cite the source of every cost: the purchase order and date for material, the closed job or routing for hours, and our recorded rates for labor and burden. If a rate is missing, name it, list the lines it blocks and give no total. Spread setup separately at each quantity, keep margin on its own line, and flag any tolerance we have not held before. Check the requested date of {due_date} against {shop_load_file}. Give me a customer quote with no hours, rates or margin in it, plus a separate internal cost sheet. Do not send anything.
The original skill is published by anthropics on GitHub (anthropics/claude-plugins-official). Open it there to install or import it; the prompt above is our own adaptation.
What can go wrong?
- Typing a labor rate into the chat to get a number faster. The skill ignores ad hoc rates on purpose; record the rate in setup instead.
- Quoting a tolerance tighter than the shop has proven. Read the capability flags before the price.
- Skipping the planning export. Without it, the lead time is labeled as unchecked, and that label belongs in front of the customer conversation.
- Anthropic labels the plugin a reference implementation it does not actively maintain, so rebuild a few recent quotes with it before relying on it.
Our take
In most small job shops, the quote lives in one estimator's head and a spreadsheet only they understand. That works until they are on vacation or a customer disputes a number months later. This skill's best idea is that a price is only useful if you can explain it, so every line points to a purchase order, a closed job or a standard cost, and the margin sits on its own line where the estimator can see their negotiating room. Its refusals are equally valuable. With no confirmed labor rate it will not invent one or sneak a ballpark through past prices, and it flags a tolerance the shop has never held before anyone commits to it. The split between a customer quote and an internal cost sheet is also sensible, since internal hours and margin should never leak into what the buyer receives. The setup is real work, and the plugin is labeled a reference implementation, so trial it on recent jobs. In our dry run on a fictional bracket order with three quantity breaks, it priced material from a dated purchase order, blocked totals until the burden rate was set and flagged the requested date as too early.
Where the time goes back: Estimators spend much of each quote hunting for the last price paid, the hours on a similar job and the current shop load. Having those pulled and cited leaves them to apply judgment, and a counteroffer becomes an edit rather than a rebuild.
FAQ
What happens if a rate is missing?
Why two documents?
Who made it and what license does it use?
Source and credit
This playbook is based on work by anthropics. We summarize it and link to it and write our own adapted prompt.
- Original
- quote-build skill (anthropics/claude-plugins-official, Claude for Manufacturing)
- Creator
- anthropics
- Published on
- GitHub (anthropics/claude-plugins-official)
- Original date
- Nov 12, 2026
- License
- Apache-2.0
- Originally for
- Claude
- AI dry run
- Nov 15, 2026: passed. Dry-run tested by our AI test agent on sample input. No invented rate, costs cited, setup re-amortized, margin separate, date checked, customer quote clean.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Nov 15, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
The original is licensed under Apache-2.0 by anthropics. Modified: our adapted prompt and summary are our own wording; the original skill {"was unchanged at the source when we snapshotted it (live source later removed)" if src_removed(s) else "is unchanged at the source link"}.
Are you the creator? Claim or correct this page.