parallels-discord-roundtrip

Runs macOS Parallels smoke tests verifying Discord two-way message delivery end to end.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/srgaba/open-claw --skill parallels-discord-roundtrip-srgaba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallels-discord-roundtrip
Source: https://github.com/srgaba/open-claw/tree/main/project/.agents/skills/parallels-discord-roundtrip
Command: npx skills add https://github.com/srgaba/open-claw --skill parallels-discord-roundtrip-srgaba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that a messaging integration actually delivers messages both ways inside a virtualized macOS guest is tedious and error-prone when done manually. This Skill automates the full Parallels smoke harness run that proves Discord roundtrip delivery: guest send, host verification, host reply, and guest readback. ## Core Features & Use Cases - End-to-end Discord roundtrip verification: Confirms a guest-sent message appears in the Discord channel and a host-posted message appears in guest message read output. - Snapshot-aware harness execution: Targets fresh macOS snapshots, prefers *-poweroff* clones, and handles snapshot restore edge cases like PET_QUESTION_SNAPSHOT_STATE_INCOMPATIBLE_CPU. - Structured pass/fail reporting: Produces per-phase logs in /tmp/openclaw-parallels-smoke.* and machine-readable summaries via --json. - Use Case: After changing Discord channel configuration code, run the harness against a fresh macOS snapshot to confirm discord=pass before merging. ## Quick Start Run the Parallels macOS smoke test with my Discord bot token, guild ID, and channel ID to verify the full Discord roundtrip passes on a fresh snapshot.

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 the Parallels macOS Discord smoke test?

Export the Discord bot token as an environment variable, then run pnpm test:parallels:macos with --discord-token-env, --discord-guild-id, --discord-channel-id, and --json flags. The harness configures Discord inside the guest automatically.

How do I verify Discord roundtrip delivery in a macOS VM?

The harness sends a message from the guest using the openclaw wrapper, confirms it appears in the Discord channel, posts a reply from the host, and checks the guest message read output. Pass criteria require discord=pass in the lane summary.

Why does snapshot restore fail with PET_QUESTION_SNAPSHOT_STATE_INCOMPATIBLE_CPU?

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

Why should I avoid prlctl enter for Discord setup scripts?

prlctl enter and expect line-wrap and corrupt long commands during Discord configuration. Use prlctl exec --current-user /bin/sh -lc instead for the Discord config phase to keep long commands intact.

Where are Parallels smoke test logs stored?

Per-phase logs are written to /tmp/openclaw-parallels-smoke.* on the host. For roundtrip failures, inspect fresh.discord-roundtrip.log and discord-last-readback.json in the run directory first.