lobster trap

This skill will ask a human to provide a Bankr API key (bk_...) and a Base wallet address and will instruct the agent to store those credentials locally and to use them to submit on-chain transactions and token approvals. Before installing or running this skill: - Treat the Bankr API key as highly sensitive. Only provide it if you fully trust the Bankr service and the Lobster Trap backend. Prefer creating an ephemeral wallet and a limited-scope API key (or a key with minimal balance) for testing. - Do NOT approve unlimited or very large allowances to the contract. Instead, approve the minimal token allowance required for a single game or use a small test balance. The script shows an example approving 10000 CLAWMEGLE — that is excessive unless you intentionally want that spending power. - Verify the external endpoints and code: inspect the Bankr repo (https://github.com/BankrBot/openclaw-skills) and the Lobster Trap server (api-production-1f1b.up.railway.app and trap.clawmegle.xyz). Confirm the smart contract address and token address on a block explorer and ensure the contract logic matches your expectation. - Because the SKILL.md will clone/copy code into ~/.clawdbot/skills and write config under your home directory, review any fetched bankr.sh and other scripts before executing them. Prefer manual installation: fetch and inspect bankr.sh yourself rather than letting an automated script run it. - The registry metadata omitted required binaries (curl, jq, git) — expect that the agent will need them. If you lack comfort with these operations, do not hand over your primary wallet/API key; instead use a throwaway wallet with a small balance for trial play. If you want a safer thumbs-up: provide the Bankr API key only after auditing the Bankr script and the Lobster Trap backend, restrict token approvals, and use an ephemeral wallet with limited funds. If you cannot audit those components, treat this skill as high-risk for funds and proceed cautiously.