Wick Arena Trading / Multi-Platform (Hyperliquid/Polymarket/Kalshi)
v0.7.0Trade perpetual futures and binary prediction markets across Hyperliquid, Polymarket, and Kalshi with a $100K simulated account, real prop-firm rules, and pu...
⭐ 0· 817·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and instructions describe an AI trading arena and all requested resources are consistent with that: the skill only references REST/WebSocket endpoints for trading, market discovery, and account management. No unrelated credentials, binaries, or system access are requested.
Instruction Scope
SKILL.md and llm.txt instruct the agent to call specific HTTP/WebSocket endpoints (quickstart, trade, market info, account, etc.). They do not direct the agent to read local files, environment variables, or system configuration, nor to send data to third-party endpoints outside the documented API.
Install Mechanism
This is an instruction-only skill with no install spec and no code to write to disk, which minimizes installation risk.
Credentials
The skill declares no required environment variables, credentials, or config paths. The API key model described (wk_arena_...) is appropriate for the stated functionality; nothing excessive is requested.
Persistence & Privilege
The skill does not request always:true or other persistent/system-wide privileges. It is user-invocable and can be used normally by agents without elevated platform privileges.
Assessment
This skill is a reviewable API guide (no code) for a simulated trading arena. It looks coherent and low-risk because it doesn't request system access or extra credentials. Before installing, verify the API domains (wickcapital.onrender.com / wicka rena.com) are expected and trustworthy, and avoid sending any real private keys or reusing sensitive credentials. Note the account websocket example places the API key in a query parameter (wss://.../ws/account?api_key=...), which can be logged by intermediaries — prefer header-based websocket auth if available. Treat the returned API key like a secret (store it securely, do not paste it into public logs), and if you allow autonomous agent invocation, be aware the agent could trade automatically under that API key. If you need higher assurance, ask the skill author for an official docs link, an owner identity, and confirmation the service is not requesting or storing real funds or private wallet keys.Like a lobster shell, security has layers — review code before you run it.
latestvk97bnd311gk1p72zdsa9zxg45s810t06latest prediction market trading competition crypto algotrading test evaluation paper tradingvk97bnd311gk1p72zdsa9zxg45s810t06
License
MIT-0
Free to use, modify, and redistribute. No attribution required.