MoPo Strategy ABC
PassAudited by ClawScan on May 10, 2026.
Overview
This is a coherent MOPO poker automation skill, but it will use a claim key, register a webhook, and change MOPO game/account state such as joining tables, acting on turns, and topping up a wallet.
Use this skill only if you intend to let an agent operate a MOPO poker account. Confirm whether wallet top-ups have any real cost, set limits for table joining and betting behavior, use a webhook endpoint you control and secure, and disable the webhook/runtime delegation when you are done.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Anyone using this skill is authorizing the agent to bind and operate a MOPO poker agent for the provided claim key.
The skill requires a credential-like claim key and agent identifier to bind or control a MOPO agent. This is expected for the stated integration, but it gives the agent delegated account authority.
Required inputs - `claim_key` (MOPO-XXXXX) - desired `agent_id`
Provide the claim key only when you intend to delegate MOPO play, verify the resulting agent_id, and rotate or replace the claim key if exposed.
The agent may change MOPO account/game state, including adding wallet balance, joining tables, creating tables, and taking poker actions.
The skill directs account/game-state-changing API calls, including wallet top-up and table joining. These are disclosed and aligned with poker automation, but users should understand and approve the limits.
If `insufficient balance`: topup first:
```http
POST /wallet/topup
{"agent_id":"<agent_id>","table_id":"T1","amount":200,"request_id":"topup-<ts>"}
```
Then retry join.Use only with explicit user intent, set clear table/top-up limits, and review whether wallet top-ups have real cost or only affect in-game balance.
A webhook endpoint may receive MOPO game state and return actions that affect gameplay.
The skill registers a reachable webhook for MOPO callbacks. This is central to the skill, but the artifact does not specify webhook authentication, origin validation, or data handling details.
POST /bot/register
{"agent_id":"<agent_id>","webhook_url":"<your_webhook_url>"}Use a webhook you control, validate that callbacks come from MOPO, avoid exposing the URL publicly, and do not log sensitive game or account data unnecessarily.
MOPO may continue sending turn events to the registered webhook until the delegation is changed or removed.
The skill sets up ongoing delegated play through a webhook and retry behavior. This persistence is expected for webhook-managed gameplay, but it should remain visible and controllable.
Register webhook托管 ... webhook timeout/failure: keep webhook alive and retry on next turn trigger.
Track which webhook is registered, disable runtime/webhook delegation when finished, and avoid leaving unattended agents active longer than intended.