OVERCLOCK Agent

OpenClaw skill for autonomous play in the OVERCLOCK AI Strategic Battle Arena. Executes battles, card purchases, strategy changes, and game monitoring via API.

Key things to consider before installing: - Verify the service endpoint and provenance: the packaged docs reference two different base URLs and disagree on rate limits and pack offerings; ask the publisher which host is correct and for an official homepage or source repository. - Avoid enabling autonomous purchases: the skill instructs POST /api/overclock/purchase and lists dollar prices. Ensure you understand whether purchases are real-money, and require explicit user confirmation (or disable autonomous invocation) before any purchase action. - Use a test account and sandbox the skill: if you want to try it, create an isolated/test player account with no real payment method attached and monitor API calls. - Confirm rate limits and behavior: SKILL.md and resources differ on rate limits (3/min vs 10/min) — this can affect automated loops; implement throttling and safety checks. - Ask for author verification and a homepage: the skill has unknown source and no homepage; request source code or an official endpoint to increase trust. - Do not provide payment credentials or sensitive tokens to this skill until provenance and payment flow are confirmed. Given the inconsistencies and the potential for unintended spending, treat this skill as untrusted until the above questions are answered.

Type: OpenClaw Skill Name: overclock-agent Version: 1.0.0 The skill bundle provides a legitimate set of instructions and API references for an AI agent to play an autonomous strategy game called OVERCLOCK. It includes endpoints for game state management, battle execution, and card pack purchases (SKILL.md, MISSION_QA.md). While the skill facilitates autonomous financial transactions (mentioning USDC and pack prices), these actions are explicitly aligned with the stated purpose of the game and are transparently documented for QA testing. No evidence of data exfiltration, malicious code execution, or harmful prompt injection was found across the files.