brikko-studio-parallels-smoke

Automate Brikko Studio Parallels guest smoke tests across macOS, Windows, and Linux VMs.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/brikkoAI/brikko-studio --skill brikko-studio-parallels-smoke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brikko-studio-parallels-smoke
Source: https://github.com/brikkoAI/brikko-studio/tree/main/packages/core/.agents/skills/openclaw-parallels-smoke
Command: npx skills add https://github.com/brikkoAI/brikko-studio --skill brikko-studio-parallels-smoke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual effort of troubleshooting and validating Brikko Studio Parallels guest workflows, including install processes, onboarding flows, gateway health checks, and upgrade paths across macOS, Windows, and Linux virtual machines, reducing release validation time and catching cross-OS regressions early.

Core Features & Use Cases

  • Cross-OS Smoke Testing: Run standardized smoke tests for Brikko Studio install, onboarding, and gateway functionality across macOS, Windows, and Linux Parallels VMs.
  • Upgrade Regression Validation: Test both fresh installs and same-guest update flows for stable, beta, and dev release channels, including npm-based and tgz-based update paths.
  • Diagnostic Support: Interpret phase logs, identify stalled installs, transport flakes, and gateway issues, and provide targeted fixes for common Parallels and Brikko Studio edge cases. Use Case: A release engineer can use this Skill to validate that a new Brikko Studio dev channel update does not break existing Windows guest installations, or debug a stuck macOS Parallels snapshot restore during smoke testing.

Quick Start

Use the brikko-studio-parallels-smoke skill to run a full Parallels smoke test for Brikko Studio's latest stable release and interpret any install or gateway failures.

Frequently Asked Questions about brikko-studio-parallels-smoke

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

FAQPage Schema
How do I run cross-OS smoke tests for install workflows in Parallels VMs?

You can run cross-OS smoke tests by automating Brikko Studio install workflows, onboarding flows, and gateway health checks across macOS, Windows, and Linux Parallels virtual machines. This validates package installs and cross-OS compatibility in isolated environments.

Can I validate upgrade regression paths for npm update channels in isolated VMs?

Yes, you can validate upgrade regression paths by testing both fresh installs and same-guest update flows for stable, beta, and dev release channels. This covers npm-based and tgz-based update paths for published and unpublished Brikko Studio releases.

How do I debug stalled installs and transport fallback flakes during Parallels smoke testing?

Debug stalled installs and transport fallback flakes by parsing phase logs to identify stalled processes and gateway issues. This diagnostic support provides targeted fixes for common Parallels and Brikko Studio edge cases encountered during testing.

Does this support snapshot-restore recovery for time-capped test lanes?

Yes, snapshot-restore recovery is supported specifically for time-capped test lanes. This ensures isolated Parallels VM environments can be quickly restored when validating Brikko Studio package installs or diagnosing gateway RPC readiness failures.

Why is my Brikko Studio gateway RPC health check failing after a Parallels VM update?

Gateway RPC readiness failures after a VM update can result from transport flakes or stalled processes. Interpreting phase logs helps identify these gateway issues, allowing you to apply targeted fixes for cross-OS regressions in the isolated environment.

What is the best way to automate Brikko Studio release validation across multiple operating systems?

Automate Brikko Studio release validation by running standardized smoke tests for install, onboarding, and gateway functionality across macOS, Windows, and Linux Parallels VMs. This reduces manual troubleshooting effort and catches cross-OS regressions early.