Best AI Agent Skills for Hardware, CAD & Robotics 2026

A bad agent skill in web development costs you an afternoon. You revert the commit, you move on. A bad agent skill wired into a 3D printer's API, a ROS node, or a KiCad netlist moves a physical machine, and the revert button is a person walking over to hit the stop switch.

That difference should change how you install things, and mostly it hasn't. The hardware corner of the agent-skill ecosystem is younger and thinner than the web corner, and a striking share of it sits at the community trust tier with no security review recorded. The tools are useful. The vetting standard people apply to them is the one they learned from installing linter plugins.

Here's what's available for CAD, electronics, robotics and firmware work in 2026, what each one is good for, and which ones I'd want to read the source of first. Every install command below was checked against the project's own README in August 2026 rather than copied from a directory listing, including ours. Trust tiers and licence fields come from our index, and those you should still confirm at the repo before a commercial commitment.

Quick Answer

The options at a glance

CAD and mechanical design

text-to-cad is the one I'd install first. It's a collection of agent skills covering CAD, robotics and hardware design, built around code-defined geometry rather than mouse-driven modelling, with build123d in the toolchain and 3MF in the output path. That matters more than it sounds: an agent is good at writing a parametric model as code and bad at dragging a fillet. Pointing the agent at the representation it can reason about is the whole trick.

npx skills install earthtojake/text-to-cad

Provider-native plugin installs also work if you prefer them: claude plugin marketplace add earthtojake/text-to-cad followed by claude plugin install cad@text-to-cad.

freecad-mcp takes the other approach, driving FreeCAD itself through the Model Context Protocol. Useful if FreeCAD is already your production tool and you want an agent inside it rather than generating files beside it. It's community-tier and unreviewed, and it runs against your local FreeCAD install.

It installs as a FreeCAD addon plus a uv-run MCP server, so you need uv on the machine rather than Node:

mkdir -p ~/.FreeCAD/Mod/
cp -r addon/FreeCADMCP ~/.FreeCAD/Mod/

Then point your MCP config at uvx freecad-mcp.

cad-mcp is the weakest entry here and I'd skip it. Its last recorded update was July 2025, which in this ecosystem is a long time to go quiet. Nothing is wrong with it that I can see. It just hasn't moved while everything around it has.

For the tool side of this workflow rather than the agent side, Autodesk Fusion 360 and Simeq cover generative design and simulation, and our full list for architects overlaps heavily with mechanical CAD buyers.

Electronics and PCB

kicad-mcp-server is effectively the only option for schematic and board work, which is an uncomfortable position for any category to be in. It exposes KiCad to an agent over MCP, MIT licensed, community tier, unreviewed.

git clone https://github.com/mixelpixx/KiCAD-MCP-Server.git
cd KiCAD-MCP-Server
npm install
npm run build

It ships example MCP configs per platform in config/ rather than a one-line install.

Use it for the parts of board design that are clerical: netlist checks, bulk footprint assignment, design-rule sweeps, BOM cleanup. Do not use it for placement or routing decisions you can't personally justify at review. An agent that confidently routes a differential pair without understanding the constraint it violated produces a board that fabricates fine and fails at test, and you find out four weeks and one fab run later.

Robotics and simulation

This is the strongest corner of the category, largely because robotics people already had a discipline of testing in simulation before touching hardware.

Genesis is a generative physics environment for general-purpose robotics and embodied AI, Apache-2.0, verified tier. It's the right place for an agent to iterate, because a policy that destroys the robot in simulation costs nothing.

ros-mcp-server connects models like Claude and GPT to robots through MCP and ROS. It's the bridge that makes the rest of the stack reachable, and at Apache-2.0 and verified tier it's the safest install in this group.

claude mcp add ros-mcp -- uvx ros-mcp --transport=stdio

It needs uv installed first, and rosbridge running on the robot side.

Two skill collections sit above these. robotics-agent-skills targets code quality for ROS1 and ROS2 work, aimed at making assistants write robotics software that survives review. robotics-skills-suite claims 76 skills spanning industrial robots, cobots, autonomous mobile robots, ROS2, and verification and validation. Both are community tier and unreviewed. Both are worth reading precisely because their value is prescriptive: they encode how a domain expert thinks, and you can evaluate that by reading it, which is not true of a compiled binary.

The line I'd hold: simulate first, always, and never give an agent write access to a live controller during development. The convenience is not worth the class of accident it enables.

Embedded, firmware and IoT

embedded-debugger-mcp wraps probe-rs for ARM Cortex-M debugging, exposed as both an MCP server and a skill. It's small, it's MIT, and it does one job. Debugging is a good fit for agent assistance because the loop is tight and the feedback is unambiguous: the register either holds what you expected or it doesn't.

iothackbot is a security-testing collection for IoT work. Treat it as you'd treat any offensive-security tooling: use it on hardware you own or have written authorisation to test, and understand that a skill designed to probe device security has, by construction, the capabilities you'd worry about in a malicious package.

mcp-3d-printer-server connects an agent to OctoPrint, Klipper, Bambu, Duet and Orca. Two things about it. It's GPL-2.0, which is the strictest licence in this list and a real consideration if you're embedding it in a commercial product rather than running it on your bench. And it controls a machine with a 250°C hot end. Sandbox it, scope its credentials to one printer, and don't leave it unattended on a long job.

Domain compliance is the surprise entry

automotive-skills-suite claims over 100 skills covering ISO 26262 functional safety, AUTOSAR, ASPICE and APQP. This is the most interesting thing in the category and the least discussed, because it isn't about generating geometry or code at all. It's about the documentation burden that surrounds safety-critical hardware, which is where automotive and industrial engineers lose their weeks.

I'd be cautious about the obvious failure mode. An agent producing ISO 26262 work products that look correct is not the same as an agent producing compliant ones, and a functional-safety assessor will not accept "the skill generated it" as provenance. Used as a drafting accelerator with a human owner on every artefact, this is valuable. Used as a shortcut through the process, it manufactures liability.

matlab-mcp-core-server rounds this out, letting an agent run MATLAB from a session. Note its licence field reads "Other" rather than a standard open-source grant, which for MathWorks-adjacent software is worth reading carefully before commercial use.

What's missing

There's no serious FPGA or HDL skill in the directory. Nothing for thermal or CFD work. Nothing for mechanical tolerance analysis, which is a discipline almost perfectly suited to agent assistance. Nothing for wiring harness design. If you're looking for a gap to build into, that list is the answer, and the automotive suite proves there's appetite for the unglamorous compliance-shaped end of it.

How to vet one before you install

Read the source. In this category that's not a pious suggestion, it's short: most of these are a few thousand lines, and the skill collections are mostly markdown you can read in twenty minutes.

Check what the tool can reach. An MCP server that talks to a printer or a robot needs credentials, and credentials scoped to one device are the difference between a bad afternoon and a bad quarter. Check the last update date; several entries here have been quiet for months. Check the licence against your actual use, because GPL-2.0 and "Other" both mean something specific if this ends up in a product.

And prefer verified-tier skills when a verified option exists. In this category it often doesn't, which is exactly why the ones that do are worth the preference.

FAQ

Are there Claude Code skills for CAD work?

Yes. text-to-cad is the strongest, covering CAD, robotics and hardware design through code-defined geometry. freecad-mcp drives FreeCAD directly over MCP if that's already your production tool.

Is it safe to let an agent control a 3D printer or robot?

Not without scoping. Give the agent credentials limited to a single device, simulate any robot behaviour before it runs on hardware, and don't leave long unattended jobs under agent control. mcp-3d-printer-server and ros-mcp-server both work well inside those limits and poorly outside them.

Why are so many hardware skills marked community and unreviewed?

The category is young and the audience is small. Web-development skills get thousands of installs and consequent scrutiny; a KiCad bridge gets neither. Ten of the thirteen entries here sit at community tier, which means you're the review process.

Can agent skills produce ISO 26262 or AUTOSAR documentation?

automotive-skills-suite generates drafts across ISO 26262, AUTOSAR, ASPICE and APQP. Treat the output as a first draft with a named human owner. An assessor will hold a person accountable for each work product, and generated provenance won't satisfy that.

What's the best starting point for a robotics engineer?

Install ros-mcp-server for the bridge and Genesis for simulation. Both sit at verified tier under permissive licences, and together they let you develop and test without hardware in the loop.