modbus-skills
v0.2.2Read-only Modbus map, byte-order, tool-generation, and capture-analysis workflows.
By Studio SeventeenLicense: Apache-2.01 GitHub starsUpdated 2 weeks ago
Directory evidence
- Runtimes
- Codex
- Parsed components
- 20 skill or MCP entries
- Source updated
- Sep 5, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install modbus-skills for Codex
codex plugin marketplace add studioxvii/modbus-skills
codex plugin marketplace upgrade modbus-skills
codex plugin add modbus-skills@modbus-skillsPaste and run these commands in a terminal with Codex. They add and refresh the modbus-skills catalog, then install this plugin.
Compatibility: the page URL and API slug “modbus-skills” remain stable.
- Codex:
modbus-skills@agent-plugin-marketplace→modbus-skills@modbus-skills
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/studioxvii/modbus-skillsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/modbus-skills/.
Plugin files
├── .codex-plugin/plugin.json├── skills/analyze-capture/SKILL.md├── skills/apply-review/SKILL.md├── skills/build-custom-export/SKILL.md├── skills/build-modpoll/SKILL.md├── skills/build-modscan/SKILL.md├── skills/build-node-red/SKILL.md├── skills/build-tool-pack/SKILL.md├── skills/capture-sample/SKILL.md├── skills/check-byte-order/SKILL.md├── skills/check-map/SKILL.md├── skills/compare-maps/SKILL.md├── skills/compile-user-map/SKILL.md├── skills/extract-pdf-map/SKILL.md├── skills/modbus-help/SKILL.md├── skills/normalize-map/SKILL.md├── skills/parse-map/SKILL.md├── skills/plan-reads/SKILL.md├── skills/remap-addresses/SKILL.md├── skills/review-evidence/SKILL.md└── skills/review-map/SKILL.md
Included Skills20
Analyze bounded Modbus samples and report communication, timing, signal, and raw-word evidence. Use when the user has capture data, JSON/CSV samples, or asks about stale, missing, flatline, or signal-quality problems.
Apply a batch of explicit Modbus map decisions while preserving evidence, exclusions, holds, and audit history. Use when the user confirms layout, exclusion, or field decisions and wants them applied to a new reviewed map.
Build a deterministic declarative text or CSV export from a documented example and canonical Modbus map. Use when the user needs a reusable text or CSV exporter and not a Node-RED, Modpoll (BETA), or ModScan (BETA) adapter.
Build deterministic read-only BETA artifacts for gavinying/modpoll or supported Witte Modbus Poll profiles. Use when the user asks for Modpoll, Witte Modbus Poll, gavinying CSV, or a Modpoll probe/final setup.
Build deterministic read-only BETA ModScan setup, poll-plan, point-map, and protocol test-message artifacts. Use when the user asks for ModScan files, a ModScan read plan, or ModScan probe/final setup.
Build deterministic read-only Node-RED Modbus flow JSON from a canonical map and compiled read plan. Use when the user asks for a Node-RED flow, Modbus flex-getter setup, or Node-RED probe/final capture path.
Build any selected combination of Node-RED, Modpoll (BETA), and ModScan (BETA) from one validated map and read plan. Use when the user wants multiple target tools, an undecided target set, or one combined probe/final pack.
Generate a bounded read-only probe pack and stop before the live Modbus read. Use when the user needs an operator-controlled sample, raw words for byte-order work, or a manual probe before decoding; the operator or enabled target tool creates capture.json only after confirmation.
Evaluate every supported byte and word layout from one immutable raw Modbus sample without choosing a winner. Use when byte order, word order, or multi-register decoding is unknown and raw words or a capture already exist.
Check a normalized Modbus map for identity, range, overlap, width, access, function, and byte-order problems. Use when the user wants deterministic lint/validation findings on a normalized or reviewed register map.
Compare two reviewed Modbus maps and report added, removed, moved, changed, and unresolved points. Use when the user compares firmware/map revisions or asks what changed between two validated maps.
Compile an OEM Modbus PDF or structured register map plus measurement intent into an organized user map, JSON, CSV, and optional target outputs in one resumable run. Use when the user wants an organized user map or offline outputs from an OEM source rather than a specialist review chain.
Extract traceable Modbus register candidates, source coverage, and page evidence from a PDF manual or bounded page range. Use when the source is a PDF register manual and the user wants extraction evidence before normalization or compilation.
Choose the next Modbus skill or short workflow from the user's goal and current artifact. Use when the user is unsure which Modbus skill to run, asks what to do next, or needs a safe path from their current artifact.
Normalize Modbus candidates into explicit offsets, areas, units, datatypes, widths, access, and byte-order states. Use when candidate rows exist and need canonical engineering fields, holds, and source-preserving normalization.
Parse structured Modbus register maps into candidate rows with source values, rejected rows, assumptions, and holds. Use when the source is CSV, JSON, XML, XLSX, or structured text and needs traceable candidate rows.
Compile validated Modbus points into deterministic, bounded read blocks for function codes 01 through 04. Use when a validated map is ready and the user needs a read plan before building Node-RED, Modpoll (BETA), ModScan (BETA), or a tool pack.
Preview and apply a known map-wide conversion between Modbus offsets and Modicon reference notation. Use when the user asks to convert 40001-style references, protocol offsets, or another known address convention across a map.
Review Modbus source evidence with automated checks and a grouped exception queue, avoiding page-by-page or row-by-row approval. Use when source evidence needs status grouping, exception decisions, or confirmation of a bounded extraction scope.
Review a raw or messy Modbus register map through parsing, normalization, linting, and grouped evidence exceptions when source review itself is the requested outcome. Use when the user wants end-to-end source-map review rather than an organized user-map compile.
Plugin manifests1
{
"name": "modbus-skills",
"version": "0.2.2",
"description": "Read-only Modbus map, byte-order, tool-generation, and capture-analysis workflows.",
"author": {
"name": "Studio Seventeen",
"url": "https://github.com/studioxvii"
},
"repository": "https://github.com/studioxvii/modbus-skills",
"license": "Apache-2.0",
"keywords": [
"modbus",
"industrial-automation",
"node-red",
"register-map",
"byte-order"
],
"skills": "./skills/",
"interface": {
"displayName": "Modbus Skills",
"shortDescription": "Read-only Modbus engineering workflows",
"longDescription": "Parse and review register maps, evaluate byte order, compile bounded read plans, generate tool configurations, and analyze captures.",
"developerName": "Studio Seventeen",
"category": "Productivity",
"capabilities": [
"Read"
],
"defaultPrompt": [
"$modbus-help Choose the next skill for my Modbus task.",
"$review-map Review this Modbus register map.",
"$check-byte-order Evaluate byte order from these raw words.",
"$build-tool-pack Build a Modbus tool pack for these targets."
],
"brandColor": "#2563EB"
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[modbus-skills on Agent Plugins Marketplace](https://pluginsmp.com/plugins/modbus-skills)