Vention skills
Version 0.10.31. Skills for coding agents that work with Vention machines, packaged as one plugin, vention, in the vention-skills marketplace.
| Skill | What it does |
|---|---|
vention-machine-logic | Write, validate, and deploy MachineLogic Python applications with the machine-logic-sdk and the Vention CLI. |
vention-machine-logic-hmi | Build the custom operator HMI of a MachineLogic application on the Vention component libraries, wired through vention-communication. |
vention-design | Create and edit Vention machine designs and design graphs through the Vention MCP server. |
vention-monitoring | Diagnose deployed machines from controller state, history, health, and activity data through the Vention MCP server. |
Install
The plugin ships as the npm package @vention/vention-skills, listed in the vention-skills catalog at
https://assets.vention.com/vention-skills/marketplace.json.
Claude Code needs 2.1.277 or later: earlier versions run a plugin package's install scripts.
The quickest route on any client is the Vention CLI:
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. |
| Codex | Always installs for your user account (Codex has no project scope). Writes a catalog directory under your home directory holding the same npm entry, then runs codex plugin marketplace add <dir> and codex plugin add vention@vention-skills. |
| Cursor, Copilot | npm pack @vention/vention-skills, then unpacks every skill the package holds into .agents/skills under your home directory or the project (per --scope), replacing those skills and leaving the rest untouched. |
| Manual | npm pack @vention/vention-skills, then copy package/skills/<skill> into your agent's skills directory. |
vention skills status lists every Vention skill on disk with its version, next to the latest version on npm. vention skills update updates every agent that has the skills: Claude Code through claude plugin update vention@vention-skills, Codex by rerunning its install, and Cursor and Copilot by unpacking the package again at the scope they were installed at. The vention-machine-logic and vention-machine-logic-hmi skills run this check at the start of each session.
Verified installs
Checked by hand against the 0.1.0 package published to a throwaway local registry, before the HMI skill was added.
| Client | Version | Status |
|---|---|---|
| Claude Code | 2.1.267 | unproven: the test machine's managed Claude Code policy only allows listed marketplaces, so it refused the local catalog URL |
| Codex | codex-cli 0.157.1 | installed and loaded: the npm package landed in plugins/cache/vention-skills/vention/0.1.0/skills/<skill>/SKILL.md and all three skills appear in the prompt Codex renders |
| Cursor | 3.22.7 | files installed in .agents/skills; client load not checked |
| Copilot | VS Code 1.114.0, Copilot Chat 0.42.3 | files installed in .agents/skills; client load not checked |
| Manual | npm 11.6.1 | files installed: npm pack plus a copy into .claude/skills |
Development
Every change goes through the vention-skills project in VentionCo/platform-products (projects/machine-code/libs/vention-skills).
npx nx build vention-skillswrites the package todist/projects/machine-code/libs/vention-skills/, stamping the package version into both plugin manifests and everySKILL.md. That directory is the npm package root and the plugin root.npx nx test vention-skillsbuilds first, then checks the frontmatter, the relative paths each skill mentions,claude plugin validate --strict, an install from the built package, and pyright over the examples.npx nx lint vention-skillslints the build and test sources.
Releasing
nx release reads the latest vention-skills@<version> tag, works out the next version from the conventional commits since it, tags it, creates a GitHub release, and publishes dist/{projectRoot} to npm through the nx-release-publish target default. npm authenticates the release job through the package's GitHub trusted publisher, so no npm token is stored.
The version in the committed package.json is only a starting point: the release run writes the new one there before building and never commits it.
The marketplace file is served from the Vention CDN, not from npm. The publish target uploads the committed .claude-plugin/marketplace.json to the vention-skills bucket on every master build that touches this project. Watchtower then pins that upload in the devops repo, and a production promotion there makes it live at the URL above.