← Back to library

Send suppliers an RFQ package that makes bids comparable

Anthropic's Claude for Manufacturing plugin, released November 12, 2026, includes a skill for sourcing parts from suppliers. It stops when the drawing revision disagrees with the ERP, keeps today's price out of the package, insists on one bid format and leaves every send and award to the buyer. We explain how to use it.

  • OutcomeUse the supplier-quote-request skill from Anthropic's Claude for Manufacturing plugin to assemble a request for quotes with the drawing at its confirmed revision, a sourced demand picture, quality clauses, commercial terms and a required bid layout, list what is missing, draft one email per supplier for the buyer to send, then read the returned bids into one shape and compare them by quantity break.
  • SetupUnder an hour
  • LevelIntermediate
  • Creditanthropics
View original
Works with
ClaudeClaude CoworkClaude Code

Published Nov 13, 2026Updated Nov 13, 2026AI dry run on sample input: passed Nov 13, 2026Source verified Nov 13, 2026

When should you use it?

  • You need quotes from new or alternate suppliers for a part, a material or an outside process
  • A quality problem has been traced to a supplier and you need another source
  • Supplier replies arrive in different formats and comparing them takes hours

Not for: Sending emails or placing orders automatically; the buyer sends and awards; Parts with export-controlled or ITAR technical data, which the skill blocks for the owner to handle; Negotiating by sharing one supplier's price with another, which it refuses to do

What do you need, and what do you get?

You need

  • The part number, drawing and specification
  • Usage history, open demand and any forecast, from the ERP or pasted
  • Your approved supplier list, standard quality clauses and commercial terms from onboarding
  • Supplier replies as emails, PDFs, spreadsheets or pasted text, when they arrive

You get

  • An RFQ package with a mandated bid structure, kept free of internal prices
  • A specific list of missing items and where each should have come from
  • A candidate supplier list with unapproved and single-source warnings
  • One draft email per supplier, plus chase drafts for late replies
  • A comparison table for each quantity break with sources, and a recommendation for the buyer

How does it work, step by step?

  1. Install and onboardAdd Claude for Manufacturing from the Claude plugin directory and record your approved suppliers, standard clauses and terms during onboarding.
  2. Ask it to source the partName the part and attach the drawing. Resolve any revision mismatch with the document owner before going further.
  3. Review the package and gapsCheck the demand figures, the clauses and the missing-items list, then release the package yourself.
  4. Send the draftsSend each supplier its own email from your mailbox and tell the assistant when they went out so it can track the due dates.
  5. Compare and decidePaste or upload the bids as they arrive, review the comparison per quantity break and make the award decision yourself.

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)

Prompt3 variables
Prepare a supplier RFQ for part {part_number}. Drawing: {drawing}. Usage and demand: {usage_data}.
Stop and tell me if the drawing revision differs from our item master.
Include the demand picture with its date range, our quality clauses and terms, a response due date and a required bid format: unit price per quantity break, tooling priced separately, lead time for first article and production, minimum order, currency, validity and exclusions.
Do not put our current price, any target price or other suppliers' names in the package.
List anything missing and where it should come from, suggest candidates from our approved list, and draft one email per supplier for me to send.

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?

  • Skipping the required bid format. Without it, suppliers answer in their own layouts and the comparison turns into manual work again.
  • Treating a silent supplier as a decline. Chase first and keep the event open until you decide to close it.
  • Letting your current price or a target price slip into the package, which tells every bidder where to land.
  • The plugin is labeled a reference implementation that Anthropic does not actively maintain, so test it on a past sourcing event first.

Our take

Buyers know the frustration: three suppliers reply in three formats, one quotes a lot price, another hides tooling in a footnote, and comparing them becomes a rebuilding exercise. This skill tackles the cause rather than the symptom by putting a required bid structure into the request itself, so every reply arrives with prices per quantity, separate tooling, lead times and exclusions. Two safeguards impressed us. The revision check against the ERP is a hard stop, which prevents the classic mistake of quoting an outdated drawing, and the package is screened so the current price, the incumbent's name and any target price never leave the building. We also like that a quiet supplier stays a no-response instead of quietly becoming a decline. Keep in mind that the buyer sends every email and makes every award, which is the right design, and that Anthropic labels the plugin a reference implementation, so trial it on a past purchase first. In our dry run on a fictional bracket sourcing event, it blocked an outdated drawing, then compared two bids and flagged a lot price that could not be treated as a unit price.

Where the time goes back: A complete package and a fixed reply format up front mean fewer rounds of supplier questions and no evening spent retyping three differently shaped quotes into one spreadsheet.

FAQ

Who made it and what license does it use?
Anthropic published it in the anthropics/claude-plugins-official repository on GitHub under the Apache 2.0 license.
Will it email suppliers for me?
No. It writes one draft per supplier, and you send them. It records the send date only when you tell it.
How does it handle bids in different currencies?
It does not convert them or rank them against each other. It shows them separately so the buyer can decide how to compare.

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
supplier-quote-request 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 13, 2026: passed. Dry-run tested by our AI test agent on sample input. Revision hard stop, internal price kept out, bids not normalized, missing fields listed, no sends, buyer decides.
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 13, 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.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminRoutine✓ AI dry run

Get the plant report ready before the morning meeting

Schedule the morning-plant-pulse skill from Anthropic's Claude for Manufacturing plugin to combine the overnight exports from planning, production and maintenance, compute output against plan, OEE and its three parts, downtime ranked by minutes and by count and the cost of losses, then refresh one operations dashboard per site with 14- and 30-day trends, all without changing any business system.

Credit: anthropics

An afternoon+
Operations & AdminSkill✓ AI dry run

Have Claude fill PDF forms, even ones with no fields

Give Claude the pdf skill so that when you hand it a form and the answers, it first checks whether the file has real form fields, fills those by their IDs if it does, places text by measured coordinates on flat or scanned forms if it does not, validates every box before writing, and renders the filled pages as images so you can see where each answer landed before you sign or send it.

Credit: Anthropic

Minutes
Operations & AdminSkill✓ AI dry run

Join plant exports and ERP data, with mismatches explained

Use the data-consolidate skill from Anthropic's Claude for Manufacturing plugin to identify each export file, check that every source covers the same dates before joining, pull matching ERP and maintenance records, normalize part and order numbers with a log of every rule applied, sort every record that fails to match into a named class with a proposed fix, and apply nothing without your yes.

Credit: anthropics

An afternoon+
Operations & AdminSkill✓ AI dry run

Rank likely root causes and draft the 8D from plant data

Use the root-cause-capa skill from Anthropic's Claude for Manufacturing plugin to line up sensor, inspection, maintenance and lot records on one checked timeline, run control-chart and clustering checks in code, rank several candidate cause chains with evidence for and against each step, name the cheapest test that separates them and draft an 8D that leaves verification and closure for people to fill in.

Credit: anthropics

An afternoon+