skills.rest
svelderrainruiz
svelderrainruizCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

vipm-cli-machine

Execute VIPM CLI commands on Windows with LabVIEW version detection and JSON output.

Updated Feb 22, 2026
Search Tags:#automation#cli#package manager#windows#vipm#labview
One-click install
npx skills add https://github.com/svelderrainruiz/labview-icon-editor-codex-skills --skill vipm-cli-machine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vipm-cli-machine
Source: https://github.com/svelderrainruiz/labview-icon-editor-codex-skills/tree/main/vipm-cli-machine
Command: npx skills add https://github.com/svelderrainruiz/labview-icon-editor-codex-skills --skill vipm-cli-machine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a safe and deterministic way to interact with the VIPM package manager command-line interface on a Windows machine, preventing unintended system changes and ensuring reliable execution.

Core Features & Use Cases

  • Safe Probing: Test VIPM commands without making actual changes to your system.
  • Deterministic Execution: Ensures commands run as expected with clear success or failure reporting.
  • LabVIEW Version Awareness: Automatically detects the correct LabVIEW version for VIPM operations.
  • Use Case: Before committing a new package to your CI pipeline, use this Skill to probe the vipm install command to ensure it would succeed without actually installing anything, verifying your package's compatibility.

Quick Start

Safely probe the VIPM CLI to check its version using the provided script.

Frequently Asked Questions about vipm-cli-machine

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely test VIPM CLI commands without modifying my LabVIEW packages?▼

You can safely test VIPM CLI commands using safety-first probing to validate operations without making actual system changes. This approach verifies command success deterministically before executing real build or install actions.

How do I detect the LabVIEW version for VIPM package manager automation on Windows?▼

Detecting the LabVIEW version for VIPM package manager automation is handled automatically by a PowerShell helper script. It identifies the correct LabVIEW version to ensure VIPM operations target the intended environment.

Can I run VIPM install commands in a CI pipeline before releasing a package?▼

Yes, you can run VIPM install commands in a CI pipeline to probe package compatibility before a release. This validates VIPM behavior safely, ensuring the installation would succeed without actually modifying the system.

What VIPM CLI operations are supported for Windows automation scripts?▼

Supported VIPM CLI operations for Windows automation scripts include build, install, uninstall, list, search, version, and about. These commands are executed via a PowerShell helper script with JSON result capture.

Why does my VIPM command fail during CI release operations on Windows?▼

VIPM commands may fail during CI release operations if VIPM behavior is not validated beforehand. Using safety-first probing and deterministic execution with clear JSON result capture prevents unintended system changes and ensures reliable command success.

Related Skills

Explore More Software Engineering Skills→
coff33ninjacoff33ninja

os-awareness

Detect the host operating system before command execution or file operations.

Community
Intermediate
PTsolversPTsolvers
40

release

Automate version bumps, compatibility updates, and Julia package releases.

Official
Intermediate
svelderrainruizsvelderrainruiz

linux-ppl-container-build

Build LabVIEW Packed Project Libraries in Linux Docker containers with preflight checks.

Community
Intermediate
carapace-shcarapace-sh
1.9k

winget

Manage Windows software packages using the Winget Package Manager CLI.

Official
Advanced