cross-platform-installer-validation

Validate Windows-hosted Unix shell installers and npm postinstall flows.

3|3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/quaid-app/quaid --skill cross-platform-installer-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-platform-installer-validation
Source: https://github.com/quaid-app/quaid/tree/main/.squad/skills/cross-platform-installer-validation
Command: npx skills add https://github.com/quaid-app/quaid --skill cross-platform-installer-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate cross-platform installer flows and ensure Windows-hosted validation properly exercises Unix-shell installers and npm postinstall paths.

Core Features & Use Cases

  • Normalize and sanitize shell scripts across platforms (e.g., fix CRLF in .sh files and ensure consistent line endings).
  • Isolate validation state locally (repo-scoped TMPDIR) to keep audits reproducible.
  • Simulate dependencies with PATH-injected fakes to deterministically exercise error paths.
  • Validate postinstall behavior on unsupported hosts using Node harnesses to mock platform/arch and network access.
  • Separate environment blockers from product blockers to surface true end-to-end blockers.

Quick Start

Run the cross-platform installer validation workflow on Windows to verify that Unix shell installers and npm postinstall flows behave correctly.

Frequently Asked Questions about cross-platform-installer-validation

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

FAQPage Schema
How do I validate npm postinstall scripts on Windows for cross-platform compatibility?

Validating npm postinstall scripts on Windows involves using a Node harness to mock platform architecture and network access, ensuring Windows-hosted validation properly exercises Unix-shell installers and npm postinstall paths.

Why does my Unix shell installer fail with CRLF line ending errors on Windows?

Unix shell installer CRLF errors on Windows occur due to inconsistent line endings in .sh files. Normalizing and sanitizing shell scripts across platforms fixes CRLF issues and ensures consistent execution during cross-platform installer validation.

What is the best way to test Unix shell installer error paths on a Windows host?

The best way to test Unix shell installer error paths on Windows is by simulating dependencies with PATH-injected fakes. This deterministically exercises error paths without requiring actual Unix dependencies to be installed locally.

Can I run cross-platform installer validation locally without affecting my global environment?

Yes, you can run cross-platform installer validation locally by isolating validation state in a repo-scoped temporary directory. This keeps audits reproducible and separates environment blockers from true product blockers.

How do I separate environment blockers from product blockers during installer release validation?

Separating environment blockers from product blockers during installer release validation requires clear isolation of validation state. Using repo-local temporary state and PATH-injected fakes surfaces true end-to-end blockers without environmental noise.