parallels-discord-roundtrip

Runs macOS Parallels smoke tests proving two-way Discord message delivery between guest and host.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/AmirulAndalib/Vilvona-AI --skill parallels-discord-roundtrip-amirulandalib
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallels-discord-roundtrip
Source: https://github.com/AmirulAndalib/Vilvona-AI/tree/main/.agents/skills/parallels-discord-roundtrip
Command: npx skills add https://github.com/AmirulAndalib/Vilvona-AI --skill parallels-discord-roundtrip-amirulandalib

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that a messaging gateway works end to end inside a fresh macOS virtual machine is hard to prove manually. This Skill automates a Parallels-based smoke test that installs on a clean macOS snapshot, sends a Discord message from the guest, confirms the host sees it, posts a reply from the host, and verifies the guest reads it back. ## Core Features & Use Cases - End-to-end Discord roundtrip proof: Guest sends a message, host verifies it in the channel, host posts a new message, and guest readback confirms delivery. - Fresh snapshot testing: Restores a clean macOS snapshot (closest to a fresh install) so onboarding and gateway health are validated from scratch. - Structured reporting: Emits per-phase logs and a JSON machine summary with pass criteria such as discord=pass per lane. - Use Case: Before releasing a gateway update, run the smoke test against a fresh macOS VM to confirm Discord two-way delivery works without leaking tokens into the repo. ## Quick Start Run the Parallels macOS smoke test with my Discord bot token, guild ID, and channel ID to prove two-way Discord delivery end to end.

Frequently Asked Questions about parallels-discord-roundtrip

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

FAQPage Schema
How do I run a Discord roundtrip smoke test on macOS Parallels?

Export the Discord bot token as an environment variable, then run pnpm test:parallels:macos with the token env name, guild ID, channel ID, and the --json flag. The harness installs on a fresh snapshot, sends and reads Discord messages, and reports pass or fail per lane.

How do I test two-way Discord bot message delivery?

Use a smoke harness where the guest sends a message with a unique nonce, the host confirms it appears in channel history, the host posts a new message, and the guest readback confirms it. Matching nonces on both directions prove two-way delivery.

What inputs are required for the Parallels Discord smoke test?

You need a host environment variable holding the Discord bot token, a Discord guild ID, a Discord channel ID, and an OPENAI_API_KEY. The harness configures Discord inside the guest, so no token is checked into the repository.

Why does Parallels snapshot restore fail with PET_QUESTION_SNAPSHOT_STATE_INCOMPATIBLE_CPU?

This error appears when restoring a suspended snapshot whose CPU state is incompatible. Drop the suspended state once, create a power-off replacement snapshot, and rerun; the smoke scripts auto-start restored power-off snapshots.

What should I check when the Discord roundtrip test flakes?

Inspect fresh.discord-roundtrip.log and discord-last-readback.json in the run directory first. Per-phase logs live under /tmp/openclaw-parallels-smoke.*, and the --json flag gives a machine-readable summary of each lane.