When should you use it?
- Quote requests arrive as drawing packs, spreadsheets, portal exports, photos or long email threads
- Your estimator spends hours pulling specs and quantities out of attachments before any real pricing starts
- You want a quick, reasoned bid or pass call on new inquiries without waiting for the customer to reply
Not for: Producing the final price or machine hours; the plugin leaves that to a separate quoting skill and your estimator; Plants without a written record of their processes, size limits, tolerance capability and certifications; Sending questions or declining work automatically; the skill drafts and recommends, people decide
What do you need, and what do you get?
You need
- The RFQ email and every attachment, or a folder or pasted document
- Your plant profile from the plugin's onboarding step: processes, envelope, capability and certifications
- Optional: Microsoft 365 and an ERP such as Oracle NetSuite or Infor M3 for past quotes and actual job costs
You get
- One intake form per inquiry with a source citation for each field
- A register of missing information and a separate register of conflicting values
- A specific list of any capability limits the request breaks
- A ready-to-send email with numbered questions for the customer
- A provisional bid, no-bid or partial recommendation per line, naming the open questions that could change it
How does it work, step by step?
- Install and set upAdd Claude for Manufacturing from the Claude plugin directory and say 'set us up' so onboarding records your systems, plant limits and vocabulary.
- Hand over the whole packageForward or upload the RFQ with all its attachments and say 'an RFQ came in'. Several parts in one package stay one inquiry.
- Review the two registersCheck what was never stated and what was stated inconsistently, and decide the conflicts yourself.
- Send the questionsEdit the drafted email if needed and send it. Tell the assistant if you changed it so later answers match up.
- Weigh the recommendationUse the provisional call and the named swing questions to decide which answers to chase first, then move bid lines into quoting.
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)
An RFQ came in from {customer}. Treat everything attached as one inquiry: {attachments}. Fill our intake form and cite the file and page for every field. Do not assume any tolerance that is not printed or covered by a stated general note. List information that is missing separately from information that conflicts, with every value and its source. Before drafting questions, check the request against our plant profile and name any specific limit it breaks. Then draft a short email to the customer with numbered questions, and give a provisional bid or no-bid for each line, naming the open question most likely to flip it. Do not price the job.
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?
- A thin plant profile weakens the capability check. Spend the time in onboarding listing real limits and certifications.
- Comparable past jobs can be old. Note the date on each one before you lean on its cost.
- Phone photos of marked-up prints can be hard to read. Treat any field flagged as unreadable as a question, not a value.
- The plugin is published as a reference implementation that Anthropic does not actively maintain, so test it on past RFQs before using it on live ones.
Our take
Quote requests are where many small manufacturers quietly lose hours. The work is mostly reading, copying and noticing gaps, and it usually lands on the most experienced person in the building. This skill is a careful answer to that problem. What stands out is its discipline: every field cites its source, missing and conflicting information are kept apart because they need different actions, and it refuses to invent a tolerance. We especially like the order of operations. Checking the plant's real limits before emailing the customer saves an awkward round of questions about a part the shop could never make. The provisional recommendation that names which answer would flip it is also practical, because it tells the estimator where to push first. Two cautions. The quality of the result depends on how honestly the plant profile is filled in, and Anthropic labels the plugin a reference implementation, so run it on a few closed RFQs first. In our dry run on a fictional two-part bracket inquiry, it separated a missing revision from a conflicting quantity and flagged a finish the shop could not provide.
Where the time goes back: The slow, mechanical part of quoting, which is reading every attachment and listing what is missing, becomes a first draft with sources, so the estimator starts from a checked form and a ready email instead of a pile of files.
FAQ
Who made it and what license does it use?
Do I need an ERP connection?
Will it decline jobs on its own?
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
- customer-inquiry-intake 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 12, 2026: passed. Dry-run tested by our AI test agent on sample input. Two registers separated, no invented tolerance, specific capability gap, provisional call with swing questions.
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 12, 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.