AirIoT driver management tool with complete list of 82 drivers. Automatically match, install, and configure AirIoT drivers based on data collection requirements. When users describe requirements like collect modbus tcp data or connect opcua server, find the driver from references/drivers.md to get the correct Install Command, run it, then use the generated directory path to create data.json config file from schema.js. Critical mapping rules: driver.properties.settings maps to device.settings, model.properties.settings/tags/commands map to tables[].device settings/tags/commands, device.properties.settings maps to tables[].devices[].settings.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
AirIoT driver management tool with complete list of 82 drivers. Automatically match, install, and configure AirIoT drivers based on data collection requirements. When users describe requirements like collect modbus tcp data or connect opcua server, find the driver from references/drivers.md to get the correct Install Command, run it, then use the generated directory path to create data.json config file from schema.js. Critical mapping rules: driver.properties.settings maps to device.settings, model.properties.settings/tags/commands map to tables[].device settings/tags/commands, device.properties.settings maps to tables[].devices[].settings.
AirIoT Driver Manager
AirIoT driver management tool for automatically matching, installing, and configuring AirIoT IoT device drivers based on user requirements.
Directory Structure
Directory structure after driver installation:
airiot/lib/driver/
└── <actual-generated-dir>/ # Directory created after running npx install
└── extracted/
├── schema.js # Driver config structure (read-only)
└── data.json # Driver runtime config (to be generated)
NOTE: The actual directory name is created automatically after running the npx install command. Use ls or check the actual directory to confirm the path.
Usage Scenarios
When users describe data collection requirements, automatically match and install from the driver list:
Example workflow:
User: "Collect modbus tcp data at 127.0.0.1 port 502 unit 1 offset 200"
