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?
- Install and onboardAdd Claude for Manufacturing from the Claude plugin directory and record your approved suppliers, standard clauses and terms during onboarding.
- Ask it to source the partName the part and attach the drawing. Resolve any revision mismatch with the document owner before going further.
- Review the package and gapsCheck the demand figures, the clauses and the missing-items list, then release the package yourself.
- 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.
- 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)
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?
Will it email suppliers for me?
How does it handle bids in different currencies?
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.