Agent skill · marketing growth · aiskillstore
okx-growth-competition
List OKX Agentic Wallet exclusive trading competitions, register users for contests, track participation and leaderboard rankings, and claim won rewards. Use when users want to list available trading competitions or trading cups, view competition rules / prize pool / total prizes, register or sign up or enroll or join a contest, check the leaderboard (who is winning) or their own rank (am I in the prize zone, what is my place), ask did I win or query participation / claim status, claim won rewards or prizes from completed competitions, see which wallet account they registered with, or submit Telegram / WeChat / Email / Twitter contact for prize delivery to top-tier winners.
Why this skill is useful
Provides specific commands and workflows for managing trading competitions on the OKX platform that the AI wouldn't reliably generate on its own.
What it needs
Requires okx account access. About 7k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
OKX Growth Competition — Trading Competition Agentic Wallet exclusive trading competitions. Full lifecycle split across focused references: Participation (discover / register / trade / registered wallet / export guard) — references/participation.md Details (rules / prize pool / four reward sections) — references/details.md Rank (leaderboard / my own rank with CASE 1/2/3 templates) — references/rank.md Claim (reward status check / atomic claim / contact collection) — references/claim.md CLI reference (commands, parameters, return schemas) — references/cli-reference.md This SKILL.md holds the global rules (facts, identity invariants, routing, output rules, time formatting, status codes, error handling) that ALL references depend on. Always read this file first; then jump into the matching reference for the user's intent. Facts about every Agentic Wallet competition Treat the following as factual ground truth when the user asks about how a competition works. The two chain-related fields play distinct, non-overlapping roles — never conflate them: chainId — single id. The claim / reward chain ONLY (rewards are paid on this chain; its contract address lives here). It is NOT a trading chain unless it also appears in participateChainIds. participateChainIds — array of ids returned by both list and detail endpoints. The trading chain set. Trades on any chain in this list count toward the same competition standing. Trading-chain set = participateChainIds. Claim chain = chainId. These are two separate concepts; the display rules below NEVER union them. 1. Chain id → display name mapping. Currently supported competition chains: 1 → Ethereum, 196 → X Layer, 501 → Solana. 2. Never tell a user "your chain doesn't count" without first checking participateChainIds. 3. myRankInfo.userTotal = 0 means the user has not yet hit the qualifying threshold or the backend metric pipeline has not picked up their trades yet — it does NOT mean the user's chain is unsupported. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/okx-growth-competition