Modbus Skills — Development skill for Claude Code

Modbus Skills

Read-only Modbus engineering workflows for Codex, Claude Code, Cursor, and other clients that implement the Agent Plugins 1.0 standard.

Turn vendor Modbus documentation into clear, usable engineering files.

Modbus Skills helps controls, commissioning, and integration engineers turn a vendor manual, spreadsheet, PDF, or existing register map into:

• a human-readable user map
• JSON and CSV exports
• bounded read plans
• optional Node-RED, Modpoll (BETA), Modbus Poll (BETA), or ModScan (BETA) files

It can also compare firmware revisions, investigate byte order, and analyze captured Modbus data.

The tools are read-only by design. They produce user maps, bounded read plans, and a short question list when the documentation is unclear.

See [when to use this](docs/when-to-use.md) and the [worked example](docs/examples/compile-user-map/README.md).

First 10 minutes

1. Add the project once. The install steps are below.
2. Ask for a user map from your local manual or spreadsheet, and name the measurements you actually need.
3. Open the three files it writes: the readable map, the JSON, and the CSV.

You can say this in plain language:

Use this manual to make a user map for temperatures, operating status,
alarms, and power. Give me a readable map plus JSON and CSV.

If you want to see the result before using a real manual, open the [worked example](docs/examples/compile-user-map/README.md). If you want help choosing the next step, ask for that.

Who this is for

Use Modbus Skills when you need to turn vendor documentation into something an engineer or polling tool can use. It is useful for controls engineers, commissioning teams, system integrators, and anyone reviewing a device map or captured Modbus data.

What you can do

If you have...	You can...
A vendor manual or register map	Build a user map for the measurements you need
A PDF, spreadsheet, CSV, JSON, XML, or text file	Extract and check regis