agentleFS
Sign inStart free
hkyutonghkyutong/OneClaw/.agents/skills/parallels-discord-roundtrip/SKILL.md

parallels-discord-roundtrip

Skill1 starsChanged 8 months agoMITView on GitHub

Run the macOS Parallels smoke harness with Discord end-to-end roundtrip verification, including guest send, host verification, host reply, and guest readback.

  • Reads credentials

We split this skill into the rules it gives an agent

6 rules. 1 is common, 0 are distinctive, and 5 are very specific to this project.

  • 1

    Common

    Most of the 13 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Use when macOS Parallels smoke must prove Discord two-way delivery end to end.

    line 8
  2. Very specific:

    If Windows/Linux snapshot restore logs show PET_QUESTION_SNAPSHOT_STATE_INCOMPATIBLE_CPU, drop the suspended state once, create a …

    line 46
  3. Very specific:

    Use the openclaw wrapper for guest message send/read.

    line 48
  4. Very specific:

    Write channels.discord.guilds in one JSON object (--strict-json), not dotted config set channels.discord.guilds.<snowflake>...

    line 49
  5. Very specific:

    Avoid prlctl enter / expect for long Discord setup scripts.

    line 50
  6. Very specific:

    If roundtrip flakes, inspect fresh.discord-roundtrip.log and discord-last-readback.json in the run dir first.

    line 55

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Parallels Discord Roundtrip

Use when macOS Parallels smoke must prove Discord two-way delivery end to end.

Goal

Cover:

  • install on fresh macOS snapshot
  • onboard + gateway health
  • guest message send to Discord
  • host sees that message on Discord
  • host posts a new Discord message
  • guest message read sees that new message

Inputs

  • host env var with Discord bot token
  • Discord guild ID
  • Discord channel ID
  • OPENAI_API_KEY

Preferred run

export OPENCLAW_PARALLELS_DISCORD_TOKEN="$(
  ssh peters-mac-studio-1 'jq -r ".channels.discord.token" ~/.openclaw/openclaw.json' | tr -d '\n'
)"

pnpm test:parallels:macos \
  --discord-token-env OPENCLAW_PARALLELS_DISCORD_TOKEN \
  --discord-guild-id 1456350064065904867 \
  --discord-channel-id 1456744319972282449 \
  --json

Notes

  • Snapshot target: closest to macOS 26.3.1 fresh.
  • Snapshot resolver now prefers matching *-poweroff* clones when the base hint also matches. That lets the harness reuse disk-only recovery snapshots without passing a longer hint.
  • If Windows/Linux snapshot restore logs show PET_QUESTION_SNAPSHOT_STATE_INCOMPATIBLE_CPU, drop the suspended state once, create a *-poweroff* replacement snapshot, and rerun. The smoke scripts now auto-start restored power-off snapshots.
  • Harness configures Discord inside the guest; no checked-in token/config.
  • Use the openclaw wrapper for guest message send/read; node openclaw.mjs message ... does not expose the lazy message subcommands the same way.
  • Write channels.discord.guilds in one JSON object (--strict-json), not dotted config set channels.discord.guilds.<snowflake>... paths; numeric snowflakes get treated like array indexes.
  • Avoid prlctl enter / expect for long Discord setup scripts; it line-wraps/corrupts long commands. Use prlctl exec --current-user /bin/sh -lc ... for the Discord config phase.
  • Full 3-OS sweeps: the shared build lock is safe in parallel, but snapshot restore is still a Parallels bottleneck. Prefer serialized Windows/Linux restore-heavy reruns if the host is already under load.
  • Harness cleanup deletes the temporary Discord smoke messages at exit.
  • Per-phase logs: /tmp/openclaw-parallels-smoke.*
  • Machine summary: pass --json
  • If roundtrip flakes, inspect fresh.discord-roundtrip.log and discord-last-readback.json in the run dir first.

Pass criteria

  • fresh lane or upgrade lane requested passes
  • summary reports discord=pass for that lane
  • guest outbound nonce appears in channel history
  • host inbound nonce appears in openclaw message read output

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free