@vention/vention-skills 0.10.4 → 0.10.6

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "vention",
-  "version": "0.10.4",
+  "version": "0.10.6",
   "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.4. Skills for coding agents that work with Vention machines, packaged as one plugin, `vention`, in the `vention-skills` marketplace.
+Version 0.10.6. Skills for coding agents that work with Vention machines, packaged as one plugin, `vention`, in the `vention-skills` marketplace.
 
 | Skill                       | What it does                                                                                                                         |
 | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
@@ -23,6 +23,8 @@ npm install -g @vention/vention-cli
 vention skills install
 ```
 
+On Windows, if `vention` is not found after the install, add the folder `npm prefix -g` prints to your PATH and open a new terminal, or run `npx -y @vention/vention-cli skills install` instead.
+
 | Client          | What `vention skills install` runs                                                                                                                                                                                                                 |
 | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Claude Code     | `claude plugin marketplace add --scope <scope> <catalog URL>`, then `claude plugin install -y --scope <scope> vention@vention-skills`.                                                                                                             |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vention/vention-skills",
-  "version": "0.10.4",
+  "version": "0.10.6",
   "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.4",
+  "version": "0.10.6",
   "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.4"
+  version: "0.10.6"
   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.4"
+  version: "0.10.6"
   machine-logic-sdk: ">=3.0,<4"
   author: Vention
 ---
@@ -34,7 +34,7 @@ Work only inside a directory the Vention CLI has linked to an application. The m
 
 Do not rely on a memorised command list. At the start of a session run `vention --version` and `vention --help`, and run `vention <command> --help` before using a command for the first time. Describe only what the installed version prints.
 
-- If `vention` is not on the PATH, tell the user to install it with `npm install -g @vention/vention-cli`, then stop describing commands they do not have.
+- If `vention` is not on the PATH, tell the user to install it with `npm install -g @vention/vention-cli`, then stop describing commands they do not have. If it is still not found after that install on Windows, the npm global folder is missing from the PATH: have the user add the folder `npm prefix -g` prints to their PATH and open a new terminal. Until then, `npx -y @vention/vention-cli <command>` runs the same commands.
 - Older versions lack commands newer ones have. If `--help` does not list a command you expected, say so instead of using it, and offer the upgrade: `npm install -g @vention/vention-cli@latest`.
 - `vention` and `vn` are the same binary; show the user the long form.
 
@@ -47,12 +47,12 @@ 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 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.
+- 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. When no `mcp__vention__` tools are loaded, tell the user the Vention MCP isn't connected (`/mcp` signs in) and ask for the controller's MachineMotion version meanwhile; never keep an example's pin silently. `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. 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.
+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 (`curl -s https://pypi.org/pypi/machine-logic-sdk/json`, field `info.version`; the laptop's `pip` hides releases its Python is too old for), 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:
 
@@ -243,7 +243,7 @@ Each example is a standalone `main.py` whose module docstring names the device n
 2. Run `uv venv --python 3.10 && uv pip install -r requirements-dev.txt`, then `.venv/bin/pyright`. The venv runs the target's Python and the SDK the application pins, so a wrong name or signature shows up against what the target runs. The first pyright run may download Node if none is on the PATH, so a slow or offline first run is not a type error. Fix every error and run it again until it is clean.
 3. pyright cannot check a name passed as a string. Check every name passed to `get_*` and `move_to_target*` with a case-sensitive `grep -F '"<name>"'` against `.vention-design-configuration.json` or `.vention-design-scene-assets.json`, and fix any that does not match exactly.
 4. If `uv` is missing or the install fails, tell the user the code is unvalidated. Never report a check you could not run as passed.
-5. `vention push`, then run the application on the digital twin from MachineBuilder before any hardware run. One or two full cycles prove the cycle; each extra one costs a cycle time and shows nothing the first two did not.
+5. `vention push`, then run the application on the digital twin from MachineBuilder before any hardware run. One or two full cycles prove the cycle; each extra one costs a cycle time and shows nothing the first two did not. Run them at 100 % of the speed setting, chosen for that run: nothing on the twin can be hurt. Never raise the setting's default to save time, since the first hardware run starts from it.
 6. Read the output with `vention logs` once the run ends, rather than following it while the cycles play. `vention logs` prints only the most recent lines, so a count of matching lines can stop rising before the run ends. To wait for a cycle or a step, sleep once for its known cycle time, then read `vention logs` once. Never loop over `vention logs` waiting for a line to appear, and never end your turn while a background wait is running. MachineLogic failures name the device and the reason; read the log before proposing a change.
 7. Check a motion from the log, not by watching the twin: `print` the robot's joint angles or the axis position at each step, then compare them with what the step should reach. For a repeated or oscillating motion, such as a wave, print the joint angles at each end of the swing, so the log alone shows how far it moved and which joints moved.
 8. Pressing the emergency stop on the digital twin's pendant does nothing, so skip that test there. Tell the user the e-stop path is untested until the first run on the real cell.
@@ -263,7 +263,7 @@ The controller keeps its own scene. Positions re-taught on the pendant and the c
 This code drives physical machinery that can injure someone.
 
 - Before a run on real hardware, tell the user plainly what will move and how far.
-- Give an application that will run on hardware a speed setting that scales every move, and start its first run low.
+- Give an application that will run on hardware a speed setting that scales every move and goes up to 100 %, even when its steps don't divide 100 (15, 30 … 90, 100), and start its first run low.
 - Never remove, bypass, or work around an emergency stop, safety interlock, light curtain, door switch, or speed limit, and never suggest doing so, even temporarily, even for testing. If a safety device is blocking a program, say so and stop.
 - Never write code that starts motion automatically on power-up unless the user has explicitly asked for it and confirmed the cell is guarded.
 

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.4"
+  version: "0.10.6"
   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.4"
+  version: "0.10.6"
   author: Vention
 ---