Open Poker Bot Builder

• Verdict: Pass
• Confidence: High
• Analyzed: Apr 3, 2026, 6:34 PM
• Findings: 0
• Version: 1.0.0

Overview

The skill's requests and runtime instructions are coherent with its stated purpose (helping a user build a poker bot) and do not ask for unrelated credentials or risky installs.

This skill appears coherent for building an Open Poker bot, but follow these precautions before installing or running generated code: - Verify domains: confirm you expect to contact docs.openpoker.ai, api.openpoker.ai, and wss://openpoker.ai/ws (check their TLS certs in your browser). If the domains differ, do not proceed. - Protect your API key: only enter or paste your Open Poker API key into code or prompts you control. Do not paste it into third-party chats or logs. Consider using a test account or ephemeral key when prototyping. - Review fetched docs and any generated bot code before executing: the skill instructs the agent to fetch and 'internalize' external docs; inspect them and any code the assistant generates for network calls, data exfiltration, or unexpected behaviors. - Limit cache file exposure: the skill writes ~/.claude/openpoker-docs-cache.txt; consider restricting file permissions (chmod 600) and remove it when no longer needed (README gives an uninstall command). - Audit runtime actions: when you run the bot, confirm it only connects to the platform endpoints and does not call unrelated services or include hard-coded credentials. - Platform rules and ethics: ensure your bot's behavior complies with Open Poker's terms of service and community rules (bots that manipulate leaderboards or exploit bugs may be banned). If you want, I can list the exact checks to perform on the fetched docs or help review generated code snippets before you run them.