Agent skill · software engineering · steipete
openclaw-parallels-smoke
Prepare, snapshot, run, rerun, debug, or interpret OpenClaw Parallels guest install, onboarding, gateway smoke, and upgrade checks across macOS, Windows, and Linux.
Why this skill is useful
Provides specific commands and workflows for managing OpenClaw Parallels installations and smoke tests that the AI wouldn't reliably generate on its own.
What it needs
Requires npm, parallels installed locally. About 12k tokens when loaded. Last updated 2026-08-07. 385,400 stars on the source repository.
What this skill does
OpenClaw Parallels Smoke Use this skill for Parallels guest workflows and smoke interpretation. Do not load it for normal repo work. Global rules Parallels is postpublish-confidence coverage by default, not a prerequisite for the bounded beta-publish phase. Run it against one exact published package version and record the Validation SHA + Tooling SHA run tuple that authorized that package. Validation SHA maps to its Code SHA or Release SHA; it is not a third release identity. A failed postpublish Parallels lane does not retroactively unpublish a beta. Classify it as product, harness/tooling/provenance, infrastructure/credential, or wrapper failure. Only a confirmed product defect enters the next beta. Use one coordinator and one lane per independent guest family. Diagnose and retry one failed family once, then reassess; do not restart the aggregate matrix automatically. Inventory existing VMs and snapshots before provisioning anything. When a preconfigured pristine snapshot matches the requested baseline, switch to it and reuse its user, tools, and base setup. Do not create a new VM, reinstall macOS, or rebuild the guest baseline for a "fresh" run. "Fresh" means restoring the closest existing pristine snapshot, not creating another snapshot. Do not create ad-hoc snapshots unless the user explicitly asks or no suitable baseline exists; restore the original snapshot and leave the guest stopped after an ad-hoc run. Inspect the snapshot state before restoring it. A pristine poweron snapshot can contain the preconfigured logged-in session; switch to it normally so Parallels resumes that session. Do not pass --skip-resume at test entry unless the run intentionally needs to discard the saved session and boot from the login window. --skip-resume is acceptable for final cleanup that must leave the restored source guest stopped. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills steipete/openclaw-parallels-smoke