How do I install the Linux Ppl Container Build skill?

Run npx skillmds@latest add tomevault-io/linux-ppl-container-build in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Linux Ppl Container Build safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Linux Ppl Container Build?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Linux Ppl Container Build free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Linux Ppl Container Build?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Linux Ppl Container Build by tomevault-io

Name: Linux Ppl Container Build
Author: tomevault-io

Linux Ppl Container Build

Build LabVIEW packed project libraries (PPL) via the Linux Docker container parity lane with deterministic preflight checks, bitness-aware artifact expectations, and failure diagnostics. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Linux PPL Container Build Skill

Use this skill when the request asks to build a PPL through Linux Docker/container parity or to diagnose Linux container PPL build failures.

Inputs expected

Target repository path and branch/SHA context.
Build intent and target bitness (64 or 32).
Target output filename (for example lv_icon_x64.lvlibp or lv_icon_x86.lvlibp).
Linux container image/tag used by parity pipeline.

Guardrails

Verify repo contains .lvversion and expected project/build spec metadata.
Verify the Linux container parity build lane is enabled for the run/profile.
Run only the Linux container PPL path when requested; do not substitute host builds.
Capture and surface container logs and status files when build fails.

Success criteria

PPL artifact generated for requested bitness and named per pipeline convention.
Artifact is published to the workflow artifacts set.
Build logs are available for diagnostics.
No hidden fallbacks to non-container execution paths.

Suggested operator checklist

Confirm image pull succeeded.
Confirm parity script step executed in container context.
Confirm output artifact path exists before upload.
Confirm final artifact is present in run artifacts.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

Frequently asked questions