EMS Builder AI Configuration Skills
Provide the Skills to an AI Agent together with the target device connection, account, and configuration requirements. The Agent can configure the current Edge-EMS Builder using the included documentation. Packages contain API fields, enumerations, complete workflows, request examples, and invocation tools; backend source access is unnecessary.
Where to start
Section titled “Where to start”For first-time use, download the complete package and ask the Agent to break down your requirements with aems-configure. This entry point is also available separately and includes guides for all configuration domains and contracts for the current 196 registered APIs.
- Extract the Skill folders. For Claude Code, place them in the project’s
.claude/skills/; for Codex, use.agents/skills/. - Provide the Edge-EMS Builder base address: LAN
http://<device-address>:8988(without/api), or proxyhttps://<device-UUID>.proxy.jelina.wise-iot-cloud.com/api. Use the port configured on the device. - Provide login information or a Token in the current environment, and describe the objective, scope, and existing devices/points.
- The Agent first queries current state and dependencies, validates requests, configures objects in sequence, and reads back results. It also tracks asynchronous tasks to their final state.
Credentials need not be written into Skill files. Each configuration Skill includes its own domain contracts and invocation tools. Downloading only one Skill does not require other Skill folders. Tools support offline field lookup and validation. Actual HTTP calls use the Python 3.10+ standard library; real-time reads/writes also have a Node.js 22+ client.
Full-featured entry point
Section titled “Full-featured entry point”| Skill | Purpose | Download |
|---|---|---|
aems-configure |
Complete configuration orchestration, including all APIs, domain guides, and invocation tools | ZIP |
Data and device templates
Section titled “Data and device templates”| Skill | Purpose | Download |
|---|---|---|
point-table-to-commbridge-excel |
Convert point lists into CommBridge import Excel files, currently focused on Modbus Client | ZIP |
aems-collection-config |
Synchronize acquisition configuration and maintain identifiers, aliases, units, and cleanup scope | ZIP |
aems-add-aggregation |
Configure aggregation expressions, initial values, and runtime variables | ZIP |
aems-time-schedule |
Configure date-specific or daily repeating time schedules | ZIP |
aems-data-groups |
Manage hierarchical groups, point mappings, ordering, and moves | ZIP |
aems-ude |
Fully configure types, instances, aggregation/group/sharing templates, and materialization | ZIP |
aems-ude-placeholders |
Configure rule sets, placeholders, and matching rules; run trials, preview impact, and reconcile | ZIP |
Strategies and communication
Section titled “Strategies and communication”| Skill | Purpose | Download |
|---|---|---|
aems-lua-script |
Write and validate aggregation, trigger, MQTT, and alarm scripts | ZIP |
aems-add-trigger-plan |
Configure triggers, conditions, actions, post-processing, and activation | ZIP |
aems-alarm-lifecycle |
Manage alarm types, records, and event recovery/resolution workflows | ZIP |
aems-add-mqtt |
Configure connections, publishing, subscriptions, and responses | ZIP |
aems-device-sharing |
Configure devices, shared targets, and bindings to multiple sharing configurations | ZIP |
aems-write-data |
Real-time subscriptions, reads/writes, and remote control result verification | ZIP |
Analysis and retention
Section titled “Analysis and retention”| Skill | Purpose | Download |
|---|---|---|
aems-history-chart |
Query details, statistics, and bounded trend charts | ZIP |
aems-forecast |
Estimate trends on the Agent side, explaining methods and error | ZIP |
aems-history-export |
Create, track, and download asynchronous historical exports | ZIP |
aems-history-archive |
Manage multiple archive plans, storage targets, and failure retries | ZIP |
Accounts and operations
Section titled “Accounts and operations”| Skill | Purpose | Download |
|---|---|---|
aems-account-management |
Create users, assign roles, and maintain accounts and passwords | ZIP |
aems-runtime-config |
Modify supported runtime parameters and check environment overrides and retention policies | ZIP |
aems-backup-restore |
Back up configuration, restore under maintenance freeze, and clean up by category | ZIP |
aems-display-config |
Read/write display configuration JSON using the existing frontend structure | ZIP |
aems-system-maintenance |
Comprehensively check capacity, configuration, maintenance status, and control logs | ZIP |
Configuration and validation boundaries
Section titled “Configuration and validation boundaries”Skills are governed by APIs implemented on the target device and by account permissions. Protocol driver configuration belongs to the external CommBridge system; display configuration requires the actual frontend format. Unavailable APIs are not treated as supported features. Validate strategies, control, and data cleanup within a defined scope. Acceptance of a request does not mean a device operation or asynchronous task has completed.
Public packages contain only generic examples, without customer point lists, strategies, or credentials. Further reading: UDE, Alarms, History and archiving, System maintenance.