enclawed-parallels-smoke

Validate Parallels-based Enclawed smoke and upgrade workflows across guest operating systems.

2|Updated May 23, 2026
One-click install
npx skills add https://github.com/enclawed/enclawed-oss --skill enclawed-parallels-smoke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enclawed-parallels-smoke
Source: https://github.com/enclawed/enclawed-oss/tree/main/.agents/skills/enclawed-parallels-smoke
Command: npx skills add https://github.com/enclawed/enclawed-oss --skill enclawed-parallels-smoke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from Parallels-based Enclawed verification by guiding end-to-end smoke runs, upgrade checks, and rerun diagnosis across guest operating systems.

Core Features & Use Cases

  • Cross-platform VM coverage: Coordinates macOS, Windows, and Linux guest lanes with the right snapshot and transport rules for each environment.
  • Smoke and upgrade validation: Covers fresh install flows, latest-release-to-main upgrade checks, snapshot retests, and same-guest update verification.
  • Failure interpretation: Helps diagnose gateway readiness issues, transport flakes, timeout conditions, and log signatures from nested phase outputs.
  • Optional integration checks: Supports Discord roundtrip verification when token, guild, and channel inputs are provided.

Quick Start

Ask for the Enclawed Parallels smoke workflow for the target guest family, and have it run the correct lane, interpret the logs, and recommend the safest rerun or fix.

Frequently Asked Questions about enclawed-parallels-smoke

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

FAQPage Schema
How do I run cross-platform VM smoke tests across macOS, Windows, and Linux guests?

Cross-platform VM smoke tests involve coordinating macOS, Windows, and Linux guest lanes with the correct snapshot and transport rules for each environment. This validates fresh install flows while applying guest-specific timeout handling.

What is the best way to validate release-to-dev upgrade workflows in Parallels VMs?

Validating release-to-dev upgrade workflows in Parallels VMs requires running latest-release-to-main upgrade checks and same-guest update verification. This ensures snapshot retests pass and gateway readiness is verified before deployment.

How do I diagnose gateway readiness issues and transport flakes from nested phase logs?

Diagnosing gateway readiness issues and transport flakes requires interpreting log signatures from nested phase outputs. You analyze these logs to identify timeout conditions and determine the safest rerun or fix for the failed VM scenario.

Can I perform snapshot recovery and retests for Enclawed VM testing?

Yes, you can perform snapshot recovery and retests for Enclawed VM testing. The workflow covers snapshot restores and rerun diagnosis, allowing you to select the right snapshot and verify stability across guest operating systems.

Do I need specific credentials to run Discord roundtrip checks during VM smoke testing?

To run Discord roundtrip checks during VM smoke testing, you need to provide specific token, guild, and channel inputs. This optional integration verifies end-to-end communication when those credentials are supplied.

Why do my Parallels VM smoke tests fail with timeout conditions across different guest operating systems?

Parallels VM smoke tests fail with timeout conditions when guest-specific timeout handling is not properly configured. You must adjust timeout parameters and verify gateway readiness to resolve these nested phase failures.