openclaw-parallels-smoke

Orchestrate Parallels smoke runs of OpenClaw across macOS, Windows, and Linux.

7|12|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/borealBytes/my-farm-advisor --skill openclaw-parallels-smoke-borealbytes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-parallels-smoke
Source: https://github.com/borealBytes/my-farm-advisor/tree/main/.agents/skills/openclaw-parallels-smoke
Command: npx skills add https://github.com/borealBytes/my-farm-advisor --skill openclaw-parallels-smoke-borealbytes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenClaw Parallels smoke and onboarding validation across macOS, Windows, and Linux, consolidating installs, upgrades, and health checks into repeatable scenarios.

Core Features & Use Cases

  • orchestrates multi-guest Parallels lanes for fresh and upgrade paths
  • reads and interprets gateway status, agent turns, and logs to provide actionable feedback
  • collects artifacts and summaries for auditing and regression testing

Quick Start

Run the smoke tests using the default fresh mode for macOS, Windows, and Linux, then reproduce a targeted lane with upgrade or upgrade-from-packed-main as needed.

Frequently Asked Questions about openclaw-parallels-smoke

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

FAQPage Schema
How do I automate smoke testing across macOS, Windows, and Linux Parallels guests?

Parallels smoke testing across macOS, Windows, and Linux is orchestrated by coordinating multi-guest lanes to validate installation, onboarding, and update paths in a deterministic, logged workflow.

What does a Parallels smoke test validate for OpenClaw environments?

A Parallels smoke test validates OpenClaw environments by checking fresh installs, upgrades, gateway health status, agent turns, and onboarding workflows to ensure system reliability across operating systems.

Do I need Parallels guests to run multi-OS OpenClaw smoke tests?

Yes, running multi-OS OpenClaw smoke tests requires Parallels-enabled guests and access to a current OpenClaw environment to execute the coordinated, multi-lane validation workflow.

How are smoke test logs and gateway status results captured for auditing?

Smoke test logs and gateway status results are captured as phase logs under /tmp/openclaw-parallels-* directories and outputted as summary JSON and Markdown files containing per-lane results for auditing.

Can I run targeted upgrade scenarios instead of a full fresh install smoke test?

Yes, you can run targeted lane scenarios using upgrade or upgrade-from-packed-main modes instead of the default fresh mode to test specific OpenClaw update paths.

What happens if a Parallels smoke test lane exceeds its time limit?

If a Parallels smoke test lane exceeds its time limit, the workflow enforces per-lane timeouts to halt the process, ensuring deterministic execution and capturing any partial logs for that lane.