parallels-discord-roundtrip

Validate Discord message roundtrip delivery between Parallels guest and host.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/JOHNNYWHITEMIKE/openclaw --skill parallels-discord-roundtrip-johnnywhitemike
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallels-discord-roundtrip
Source: https://github.com/JOHNNYWHITEMIKE/openclaw/tree/main/openclaw/.openclaw/openclaw/.agents/skills/parallels-discord-roundtrip
Command: npx skills add https://github.com/JOHNNYWHITEMIKE/openclaw --skill parallels-discord-roundtrip-johnnywhitemike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifying that a guest-to-host message path reliably delivers to Discord and that a newly posted host message is observable back in the guest is error-prone and hard to validate manually during macOS Parallels smoke testing.

Core Features & Use Cases

  • Guest-to-Discord outbound verification: Send a Discord-bound message from the guest and confirm it appears in Discord history as observed from the host side.
  • Host-to-guest inbound verification: Post a fresh Discord message from the host and confirm the guest can read it back.
  • Fresh snapshot E2E smoke coverage: Exercise installation, onboarding, gateway health, and two-way message roundtrips on a target macOS snapshot.

Quick Start

Run the Parallels macOS smoke harness in JSON mode with your Discord token, guild ID, and channel ID so it can perform the full guest send → host verification → host reply → guest readback sequence.

Frequently Asked Questions about parallels-discord-roundtrip

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

FAQPage Schema
How do I verify Discord message delivery between a Parallels guest and host?

Discord message delivery is verified by running a smoke harness that sends a message from the guest, confirms it in Discord host-side history, posts a reply, and validates guest readback. This validates full two-way message roundtrip visibility on macOS Parallels.

What environment variables do I need for macOS Parallels Discord end-to-end testing?

macOS Parallels Discord end-to-end testing requires a Discord bot token via OPENCLAW_PARALLELS_DISCORD_TOKEN, a guild ID, a channel ID, and an OPENAI_API_KEY. These variables execute the deterministic harness and confirm pass criteria for the smoke run.

Does Discord roundtrip testing work on fresh macOS Parallels snapshots?

Yes, Discord roundtrip testing is specifically designed for fresh macOS Parallels snapshots and upgrade lanes. The smoke harness exercises installation, onboarding, gateway health, and two-way message roundtrips directly on the target snapshot.

How does the host-to-guest inbound Discord verification process work?

Host-to-guest inbound verification works by posting a fresh Discord message from the host side and confirming that the Parallels guest can successfully read the message back. This validates the inbound message path during smoke testing.

What is the best way to automate Discord smoke testing for a Parallels upgrade lane?

The best way to automate Discord smoke testing for a Parallels upgrade lane is running the smoke harness in JSON mode with the required bot token, guild ID, and channel ID. This executes the full guest send to host verification to guest readback sequence.

Why is manual Discord message roundtrip validation error-prone during Parallels smoke runs?

Manual Discord message roundtrip validation is error-prone because verifying guest-to-host delivery and host-to-guest observability simultaneously is difficult to track by hand. The automated deterministic harness eliminates human error and confirms strict pass criteria.