Claude for Manufacturing: 17 Skills That Draft Quotes, 8Ds and Supplier Orders Anthropic released Claude for Manufacturing, a plugin with 17 skills that drafts quotes, 8D quality reports, morning production reports and supplier orders from factory data for human review, connecting to Autodesk Fusion, Oracle NetSuite, Microsoft 365 and Infor, according to The Decoder. Anthropic's manufacturing page confirms the plugin is available on paid plans including Enterprise but does not state the skill count, and the plugin does not control physical machines; owners can require approval before a connector changes anything. No measured results were published in the launch material reviewed. Anthropic has released Claude for Manufacturing, a plugin that gives Claude access to the software factories already run and has it draft quotes, quality reports and supplier requests for human review. According to The Decoder https://the-decoder.com/anthropics-claude-for-manufacturing-plugs-ai-directly-into-factory-software-to-automate-industrial-workflows/?ref=explainx , it ships with 17 skills and works with Autodesk Fusion, Oracle NetSuite, Microsoft 365 and Infor. Anthropic's manufacturing page https://claude.com/solutions/manufacturing?ref=explainx confirms the plugin and says it is on paid plans, including Enterprise; it does not state the skill count. It does not control physical machines. This is the latest in a run of vertical plugins from Anthropic. We covered the earlier ones for creative work https://explainx.ai/blog/anthropic-claude-for-creative-work-connectors-2026 , financial services https://explainx.ai/blog/anthropic-claude-financial-services-agents-plugins-2026 and small business https://explainx.ai/blog/anthropic-claude-for-small-business-2026 . Manufacturing is the first that reaches toward the shop floor. TL;DR: what Claude for Manufacturing is | Question | Answer | |---|---| | What is it? | A plugin with 17 skills that drafts documents from factory data | | What systems? | Autodesk Fusion, Oracle NetSuite, Microsoft 365, Infor per The Decoder | | Who gets it? | Team and Enterprise customers | | Does it run machines? | No. It drafts for review and does not operate equipment | | Who approves? | Your team. Owners can require approval before a connector changes anything | | Is it proven? | No measured results published in the launch material we reviewed | What can the 17 skills actually do? Anthropic's page gives five worked examples. Each one ends with a human check. - Inspection to corrective action. Share an inspection finding and Claude writes the nonconformance report against its requirement, checks past reports for the same failure, ranks likely causes with evidence, and drafts the 8D. A quality engineer reviews and signs. - RFQ to quote. Forward a request for quote. Claude fills your intake form, lists what is missing from the drawing, and prices the job from cost history and similar past jobs. An estimator reviews the draft before it goes out. - Morning report. Claude joins overnight production, downtime and scrap exports into one report with output against plan and ranked OEE losses overall equipment effectiveness . - Machine down. Given sensor exports, maintenance history, photos and the OEM manual, Claude ranks likely causes with evidence for a technician to check and decide on. - Design variants. Claude generates variants in Autodesk Fusion from an engineer's model, scores them side by side and drafts a comparison slide. The Decoder adds that the Infor plugin can order from backup suppliers when deliveries slip and reschedule production, but only after human approval. Gripper handing a bead to a human hand, showing the human approval step in Claude for Manufacturing drafts What does an AI-drafted 8D look like? Anthropic's page embeds a long sample 8D draft, and its tone is the most telling part of the launch. The draft marks its root cause as "NOT VALIDATED", ranks three candidate causes with evidence for and against each, flags that an inspection gauge's calibration is unverified, and notes that a uniform 0.009 mm bias would put all eight readings within limits. It also lists the "cheapest discriminating test": check the gauge against a certified master. That is a deliberate design choice. The sample does not state a conclusion it cannot support, marks owners as unassigned, and keeps containment steps labeled as reported but unverified. A redaction note says a quality reviewer approved removal of seven rows of personnel names and internal identifiers. Treat it as a marketing sample, not a benchmark, but it shows what Anthropic wants the skills to do: surface gaps instead of hiding them. How do the approvals and permissions work? Anthropic lists four controls on its page: 1. Choose what Claude can see. Your team picks which systems to connect, and connectors generally follow each person's permissions in those systems. 2. Review every draft. Claude drafts quotes and reports for your team to approve. It does not operate equipment. 3. Require approval for changes. On Team and Enterprise plans, owners can require approval before a connector changes anything, or block changes. 4. Set who can use it. On Enterprise plans, admins can make the plugin available to one group or to everyone. Connectors are managed separately. Drafts also link to the drawing, requirement or record behind each figure, per both sources. That matters for audits: a reviewer can trace a number to its source. For readers building their own review loops, the pattern matches tools like Plannotator https://explainx.ai/blog/plannotator-plan-code-review-workspace-coding-agents-claude-code-codex-github-trending-2026 , which put a human checkpoint between an agent's plan and its action. What did Infor say? Anthropic's page quotes Infor CEO Kevin Samuelson: "When AI begins managing your workflows, the system underneath matters more, not less." He says Infor lets customers reach industry-specific context in Claude or in Infor, wherever they choose to work. The page also lists a separate "Infor in Claude" plugin that lets users ask questions, approve suggestions and have Infor complete tasks such as creating a purchase order or shifting production lines after unplanned downtime. The framing is consistent across the launch: the ERP stays the system of record, and Claude sits on top as a drafting and analysis layer. What is the Model Hardware Standard? The Decoder reports that Anthropic is developing a separate research preview called the Model Hardware Standard. It would connect AI agents to devices such as robotic arms and microscopes through standardized drivers. The article says Anthropic claims it cuts setup time from "weeks or months" to "hours or minutes", and that human oversight remains necessary because the AI has a limited grasp of physical processes. We could not find Anthropic's own description of this standard on the manufacturing page, so treat the setup-time claim as reported, not verified. It is the clearest sign that the plugin is a first step, not the end point. What is claimed and what is verified? | Claim | Status | |---|---| | Plugin with 17 skills for Team and Enterprise | Reported by The Decoder; Anthropic's page describes the plugin and plans | | Works with Fusion, NetSuite, Microsoft 365, Infor | Reported by The Decoder; Infor and Fusion integrations appear on Anthropic's page | | Does not control machines | Stated by Anthropic's page | | Faster quotes or fewer errors | No figures published in what we reviewed | | Model Hardware Standard cuts setup to hours | Reported by The Decoder; not verified | Anthropic's page itself advises teams to "pick one process to measure first". That is good advice, because the launch gives no before-and-after numbers. How does it compare with other Claude plugins? Anthropic's plugin approach packages skills, connectors and templates for one profession. Our knowledge-work plugins guide https://explainx.ai/blog/claude-knowledge-work-plugins-guide-2026 explains the format, and the top 25 Claude plugins https://explainx.ai/blog/top-25-claude-plugins-2026 list shows how many now exist. The manufacturing version differs in two ways: it leans on ERP and CAD connectors rather than documents, and its sample outputs are regulated-style records such as 8Ds, where traceability matters most. What will a plant manager ask first? Does Claude change my ERP data? Anthropic says vendors' systems remain the system of record, and that owners on Team and Enterprise plans can require approval before a connector changes anything, or block changes. Start with the block setting and loosen it per workflow. Can it work with systems that are not on the list? The Decoder says other systems can be integrated through file exports to Microsoft 365. That means a spreadsheet or document export can feed a skill, but it is a manual step, not a live connection. Can I edit the skills? Yes, by Anthropic's description. The page says skills are a starting point, that teams adapt them to their own forms and procedures, and that teams can build new skills for work only their facility does. This is the most important feature for regulated plants, because every quality system has its own templates. What about the model's mistakes? The sample 8D shows the intended guardrail: flag unknowns, rank hypotheses, and name a test that separates them. It does not guarantee accuracy. A reviewer still owns the sign-off, and the launch material publishes no error rates. A four-step pilot you can run this month 1. Pick one document type with a clear template and a clear reviewer, such as a quote or a nonconformance report. 2. Connect read-only first. Choose the single system that holds the records Claude needs, and keep write approval on. 3. Measure the baseline. Record how long the document takes today and how often reviewers send it back. 4. Compare after two weeks. Count edits per draft, time saved and any figure a reviewer could not trace to a source. Expand only if the traceability holds. This mirrors Anthropic's own advice to measure one process first, and it gives you the numbers the launch material does not. What this means for what you build or pay If you run or sell to a plant, the practical step is a narrow pilot: pick one workflow, such as RFQ to quote, connect read access first, and require approval on every write. Compare drafting time and error rates against your current process. If you build agents, note the design pattern: drafts with source links, ranked hypotheses with evidence, explicit "not validated" labels, and permission-scoped connectors. Those choices matter more than the model. Pricing was not stated in the material we reviewed, beyond availability on Team and Enterprise plans. Related reading Details are accurate as of November 13, 2026 and may change as Anthropic updates the plugin.