@vention/vention-skills 0.10.2 → 0.10.4

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "vention",
-  "version": "0.10.2",
+  "version": "0.10.4",
   "description": "Vention skills for coding agents: write MachineLogic applications, build machine designs, and diagnose deployed machines.",
   "author": {
     "name": "Vention"

package/README.md

@@ -1,6 +1,6 @@
 # Vention skills
 
-Version 0.10.2. Skills for coding agents that work with Vention machines, packaged as one plugin, `vention`, in the `vention-skills` marketplace.
+Version 0.10.4. Skills for coding agents that work with Vention machines, packaged as one plugin, `vention`, in the `vention-skills` marketplace.
 
 | Skill                       | What it does                                                                                                                         |
 | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vention/vention-skills",
-  "version": "0.10.2",
+  "version": "0.10.4",
   "description": "Vention skills for coding agents: write MachineLogic applications, build machine designs, and diagnose deployed machines.",
   "license": "MIT",
   "type": "module",

package/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "vention",
-  "version": "0.10.2",
+  "version": "0.10.4",
   "description": "Vention skills for coding agents: write MachineLogic applications, build machine designs, and diagnose deployed machines.",
   "author": {
     "name": "Vention"

package/skills/vention-design/SKILL.md

@@ -3,7 +3,7 @@ name: vention-design
 description: Create, build and edit Vention machine designs and design graphs for agentic layout. Use when the user wants to start a new design, lay out an automation cell, add or reposition components in a Vention design, generate a machine layout from a description, add or place a floor plan image under a design, list a design's versions, or inspect an existing design graph. Trigger on MachineBuilder designs, design graphs, assembly graphs, extrusions, actuators, robot mounting, cell footprints, floor plans, or a machine-builder URL.
 license: MIT
 metadata:
-  version: "0.10.2"
+  version: "0.10.4"
   author: Vention
 ---
 

package/skills/vention-machine-logic/SKILL.md

@@ -3,7 +3,7 @@ name: vention-machine-logic
 description: Write, edit, validate, and deploy MachineLogic Python applications for Vention machines with the machine-logic-sdk and the Vention CLI. Load it before writing or changing any Python that talks to a Vention machine, however short, since device names and version-specific SDK calls come from here. Use to program a Vention machine or MachineMotion controller, drive actuators, conveyors, robots, pneumatics, or digital I/O, change an existing application, build a state machine, debug from logs, or pull, push, or link with the Vention CLI (vention or vn). Trigger on MachineLogic, machine-logic-sdk, MachineMotion, MachineBuilder applications, the Vention CLI, or a directory holding .machine-code-app-directory-info.json. Printing what the machine or robot holds now (positions, taught targets, calibration, I/O) is a program: files on disk hold only as-designed values. Not for explaining an existing machine or its configuration in words when no program is asked for, nor for Python that never touches the machine.
 license: MIT
 metadata:
-  version: "0.10.2"
+  version: "0.10.4"
   machine-logic-sdk: ">=3.0,<4"
   author: Vention
 ---
@@ -46,13 +46,13 @@ Read `machine-logic-sdk==3.1.0` from `requirements.txt`. That is the answer. A `
 
 An application with no pin inherits whatever the target already has, and nothing on disk says what that is. Tell the user the version is undeclared and offer to add the pin. Until it is there, read the target and name the signal alongside the version:
 
-- The startup line `vention logs` prints while the application runs.
-- On a controller only, `softwareVersion` in `.vention-design-configuration.json`, read through the compatibility table on the version's documentation page. A digital twin hardcodes that field, so skip this signal there.
+- The startup line `vention logs` prints while the application runs. On a digital twin it names the twin's SDK, not a cell's.
+- The MachineMotion software version of the controller the application will deploy to, read through the compatibility table on the version's documentation page. Take it from `machine-motion-software-version` in the Vention MCP's `machine_status` for that controller's serial, and ask the user for the serial when you don't have it. `softwareVersion` in `.vention-design-configuration.json` answers only on a controller: a digital twin hardcodes it, so never read the target's version from it there.
 - `pip show machine-logic-sdk` on the user's laptop. That is the authoring environment, not the target, so label it unverified.
 
 Say `unknown` when none of them answers.
 
-Pin the version the target can install rather than the newest one: a controller has the SDK that came with its MMAI release, an existing application runs against the version it was written for, and pinned dependencies are fetched on the target, so an isolated cell resolves only what it already has. A `requirements.txt` that lists no `machine-logic-sdk` removes the SDK the application would otherwise inherit, so once that file exists the SDK belongs in it.
+Pin the version the target can install. For an application that will deploy to a controller, that is the version its MachineMotion version maps to, as above: a controller has the SDK that came with its MMAI release, and pinned dependencies are fetched on the target, so an isolated cell resolves only what it already has. With no controller yet, pin the newest release on PyPI (`pip index versions machine-logic-sdk`), which the digital twin runs, and check it against the controller's version before the first deploy. An existing application keeps the version it was written for. A `requirements.txt` that lists no `machine-logic-sdk` removes the SDK the application would otherwise inherit, so once that file exists the SDK belongs in it.
 
 With the version in hand, fetch the reference published for it:
 

package/skills/vention-machine-logic-hmi/SKILL.md

@@ -3,7 +3,7 @@ name: vention-machine-logic-hmi
 description: Build or edit the custom operator HMI of a MachineLogic application, the React touch screen in customui/ that runs in MachineBuilder and on the MachineMotion pendant, wired to the application's Python process through vention-communication. Use when the user asks for an operator screen, a custom HMI or UI, a touch panel, start and stop buttons, live machine state on screen, or recipes an operator picks, for a Vention machine or inside a directory holding .machine-code-app-directory-info.json. Uses @vention/machine-ui, @vention/machine-apps-components and @vention/machine-logic-ui-sdk. Do not use for the no-code HMI Builder, or for the Python motion logic alone (that is vention-machine-logic).
 license: MIT
 metadata:
-  version: "0.10.2"
+  version: "0.10.4"
   author: Vention
 ---
 

package/skills/vention-monitoring/SKILL.md

@@ -3,7 +3,7 @@ name: vention-monitoring
 description: Diagnose deployed Vention machines from controller state, history, health, and activity data. Use when the user reports a machine that is down, faulted, offline, slow, or underperforming, asks why a cycle time regressed, wants to interpret MachineMotion event data or drive and brake status, asks about OEE or uptime, or wants to know which machine in a fleet needs attention. Trigger on a MachineMotion serial number plus any complaint.
 license: MIT
 metadata:
-  version: "0.10.2"
+  version: "0.10.4"
   author: Vention
 ---