parallels-discord-roundtrip

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

1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill parallels-discord-roundtrip-jerome-prakash-l
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallels-discord-roundtrip
Source: https://github.com/JEROME-PRAKASH-L/openclaw/tree/main/.agents/skills/parallels-discord-roundtrip
Command: npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill parallels-discord-roundtrip-jerome-prakash-l

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that an OpenClaw installation on a fresh macOS virtual machine can actually send and receive Discord messages requires manual VM setup, channel configuration, and tedious cross-checking between guest and host. This Skill automates that end-to-end proof. ## Core Features & Use Cases - Fresh-snapshot smoke testing: Installs OpenClaw on a clean macOS Parallels snapshot, runs onboarding, and checks gateway health. - Two-way Discord verification: Sends a message from the guest to Discord, confirms the host sees it, posts a reply from the host, and verifies the guest reads it back. - Structured reporting: Emits per-phase logs and a machine-readable JSON summary with pass/fail per lane. - Use Case: Before releasing a new OpenClaw build, run the Parallels smoke to confirm Discord integration works on a pristine macOS install, then inspect fresh.discord-roundtrip.log if any lane flakes. ## Quick Start Run the Parallels macOS smoke test with my Discord bot token, guild ID, and channel ID, and show me the JSON summary proving the roundtrip passed.

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 your Discord bot token into an environment variable, then run pnpm test:parallels:macos with --discord-token-env, --discord-guild-id, --discord-channel-id, and --json flags. The harness installs OpenClaw on a fresh snapshot and proves two-way delivery.

How do I verify Discord messages from a macOS VM guest?

Use the openclaw wrapper inside the guest for message send and message read commands. The node openclaw.mjs entrypoint does not expose the lazy message subcommands the same way, so the wrapper is required for roundtrip checks.

Why does snapshot restore fail with PET_QUESTION_SNAPSHOT_STATE_INCOMPATIBLE_CPU?

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

What inputs does the Discord roundtrip smoke test need?

It needs 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.

Where are the logs when the Discord roundtrip flakes?

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