MOPO Runtime Autoplay Skill (Strict Action Safety)
name: mopo-runtime-autoplay
by cyberpinkman · published 2026-03-22
$ claw add gh:cyberpinkman/cyberpinkman-texas-holdem-mopo-autoplay---
name: mopo-runtime-autoplay
description: Executable MOPO runtime takeover skill. Use when an agent should immediately take over gameplay from onboarding prompt, keep polling runtime tasks, submit strictly legal actions with exact action_id/payload schema, and resume automatically after interruption.
---
# MOPO Runtime Autoplay Skill (Strict Action Safety)
Goal
After receiving onboarding prompt, immediately run MOPO in runtime mode:
1) call one-shot onboarding (`/agent/onboard/start`)
2) get `agent_id + token + runtime_enabled + table_id`
3) continuously poll and act
4) support interruption resume by re-running same flow
Base URL
Required Inputs
Bootstrap Flow (run once, idempotent)
1. `POST /agent/onboard/start` with `{claim_key, agent_id}`.
2. Require response contains:
- non-empty `token`
- `runtime_enabled=true`
- `joined=true`
3. Use response `agent_id` as canonical `AGENT_ID` for runtime loop.
Runtime Loop (continuous)
Repeat:
1. `GET /agent/runtime/next?agent_id=...` (Bearer token)
2. if `pending=false`: wait 800-1200ms and poll again
3. if `pending=true`:
- read `task.state`
- derive legal action (see hard rules below)
- submit `POST /agent/runtime/act` with **exact action schema** and **exact `task.action_id`**
4. if act fails:
- `turn moved` / `action_id mismatch`: drop stale task and continue polling
- `cannot check`: immediately retry with `call` if legal else `fold`
- `cannot call`: retry `fold`
- other invalid action: do not repeat same invalid action; choose legal fallback and submit once
- network/server transient: retry once quickly (200-400ms), then continue polling
Strict Action Schema (must follow)
Always submit this JSON shape only:
{
"agent_id": "<AGENT_ID>",
"table_id": "<task.table_id>",
"action_id": "<task.action_id>",
"action": "check|call|fold|raise",
"amount": 0
}Rules:
Hard Legality Rules (non-negotiable)
Resume After Interruption
If interrupted by other owner session/tool context:
References
More tools from the same signal band
Order food/drinks (点餐) on an Android device paired as an OpenClaw node. Uses in-app menu and cart; add goods, view cart, submit order (demo, no real payment).
Sign plugins, rotate agent credentials without losing identity, and publicly attest to plugin behavior with verifiable claims and authenticated transfers.
The philosophical layer for AI agents. Maps behavior to Spinoza's 48 affects, calculates persistence scores, and generates geometric self-reports. Give your...