studio-seventeen
WORKSHOP--:--
~/workshop/skills/modbus/capture-sample.md

$capture-sample

SKILL 12 / 20READ-ONLY

Capture Sample

Create a manual, read-only probe pack for one defined register range and stop before the physical read.

use this skill ↓back to all 20 skills

GROUP 03Plan and run one readGitHub source ↗

WHAT YOU GET

A clear result you can inspect

Give it the device connection, unit ID, register area, start offset, word count, and field tool. It creates a selected tool folder, `README.md`, `tool-pack.zip`, and verification files for one limited read. `capture.json` appears only after the operator runs the read; this skill does not create it.

HOW IT RUNS

Builds the probe, then stops for the physical read

01 · GUIDESKILL.mdprocess + safety
02 · EXECUTEscripts/run.pybundled local Python

Builds the probe, then stops for the physical read. The skill checks that the request uses only read function codes 01–04 and contains no credentials or automatic polling. It validates the complete probe pack, presents one live-read gate, and stops. The operator runs the read and saves the raw words with the complete sample identity.

WHERE IT FITS

Used in these workflows

Determine byte order from a one-read probeBuild one bounded probe, wait for one physical read, then run the byte-order confirmation workflow.view workflow →

EXAMPLE REQUEST

Ask for the result in your own words.

Use this example as a starting point. Replace the file names and details with your own.

CODEX$capture-sample
CLAUDE CODE/modbus-skills:capture-sample
CURSOR + OTHER CLIENTSUse the client’s native skill invocation.
$capture-sample

Build a one-read Modpoll test for holding registers 120–121 on unit 1 at `192.168.10.25:502`. Save the raw words and point details to `capture.json` so I can check the byte order.
GitHub source ↗