Agent skill

Okx Growth Competition

by internet-court in internet-court/internet-court-skill

List OKX Agentic Wallet exclusive trading competitions, register users for contests, track participation and leaderboard rankings, and claim won rewards.

MITAuto-check passedBusiness, Finance & HR

Install Okx Growth Competition

skills CLI
$ npx skills add internet-court/internet-court-skill --skill okx-growth-competition -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install internet-court/internet-court-skill okx-growth-competition --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/internet-court/internet-court-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/vendored/okx/okx-growth-competition .claude/skills/okx-growth-competition && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
okx-growth-competition
GitHub stars
6.6k
Used in
2 other repos
Token cost
~3k tokens
SKILL.md length
1,393 words
Files
7 (incl. references)
Skills in repo
80
Repo updated
First seen
Licence
MIT

At a glance

List OKX Agentic Wallet exclusive trading competitions, register users for contests, track participation and leaderboard rankings, and claim won rewards.

  • Works in 4 steps: Chain id → display name mapping.… → Never tell a user "your chain doesn't… → myRankInfo.userTotal = 0 means the user… → …
  • Users want to list available trading competitions
  • SKILL.md covers Facts about every Agentic…, Identity resolution invariant, Mandatory reading order and Pre-flight, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Okx Growth Competition is an agent skill from internet-court/internet-court-skill. 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…

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/claim.md`, `references/cli-reference.md` and `references/details.md`).

It sits in Business, Finance & HR, covering Trading and backtesting and Messaging and chat bots. It works with OKX, WeChat, Telegram and X (Twitter). The repository describes itself as: The trust layer for agent-to-agent commerce — natural-language mandates, ERC-7710 delegated permissions, x402 payments, escrow, and dispute resolution as one open, catch-all… The licence is MIT.

When your agent uses it

  • Users want to list available trading competitions
  • View competition rules / prize pool / total prizes
  • Check the leaderboard (who is winning)
  • Their own rank (am I in the prize zone

Example prompts

  • “/okx-growth-competition”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  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…
  4. competition_rank takes a single optional wallet. Omit it for self-rank — the tool sends your accountId (covers every chain in…

What it can do on your machine

Read from SKILL.md and the folder at commit fa89195. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Okx Growth Competition loads about 3k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 176 tokens; SKILL.md has 1,393 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~176
When it runs · the whole SKILL.md, loaded when a task matches
~3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~14k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from internet-court/internet-court-skill at commit fa89195, republished under its MIT licence (© internet-court). 1,393 words, ~3,039 tokens.

Download SKILL.mdSave it as .claude/skills/okx-growth-competition/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
okx-growth-competition
description
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.
license
MIT
metadata.author
okx
metadata.version
4.4.10
metadata.homepage
https://web3.okx.com

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. competition_rank takes a single optional wallet. Omit it for self-rank — the tool sends your accountId (covers every chain in participateChainIds in one call; no chain pick). Pass an explicit address ONLY when querying someone else's rank; the address chain family (EVM 0x... else Solana) must match the activity's primary chain or the tool rejects the call (no silent wrong-chain queries).

Identity resolution invariant

The query identity for competition_rank and competition_user_status is mutually exclusive: backend accepts EITHER accountId (self) OR walletAddress (cross-user) — never both. The answer to "which identity did you use?" is deterministic from the call shape.

Call shapeIdentity sent
competition_user_status (any)accountId — covers every chain in participateChainIds in one call
competition_rank without walletaccountId
competition_rank with wallet=<addr>walletAddress — tool validates addr's chain family (EVM 0x... else Solana) matches activity's chainId; mismatch → rejected
competition_claim (pre-check)accountId

For multi-activity competition_user_status (no activity_name), the same accountId is reused across all activities — backend joins by accountId.

Mandatory reading order

Before producing ANY user-facing message about a competition, you MUST first locate the matching section in the right reference file below and follow its fixed template structure. Do NOT improvise the format. Do NOT shorten the templates. Do NOT drop sections or merge them. Templates are product-mandated copy (Participation / Skill Quality wording, disclaimer) and must not be paraphrased.

The template structure is fixed; the language follows the user — see the ## Output Language rule below. When the user writes Chinese, translate the template strings to natural Chinese. When the user writes English, use English as written. Placeholders (including chain display names from {supportedChains}) stay as-is.

Quick router (user intent → reference file + section):

User intentReference fileSection
"list competitions / show available competitions"references/participation.mdStep 1 — Discover
"show details / show rules / show prize pool"references/details.mdStep 2 — View Details
"register / join"references/participation.mdStep 3 — Join
"trade for me"references/participation.mdStep 4 — Trade (delegates to okx-agentic-wallet)
"leaderboard / full board / who is winning"references/rank.mdCheck leaderboard (full board)
"my rank / what's my ranking / am I in the prize zone"references/rank.mdCheck user's own rank (across ALL leaderboards)
"show registered wallet"references/participation.mdQuery Registered Wallet
"export wallet"references/participation.mdWallet Export Guard
"check my status / did I win"references/claim.mdCheck Participation Status
"claim reward / claim my prize"references/claim.mdStep 6 — Claim Reward
Top-tier winner contact follow-up (needContact: true after claim)references/claim.mdContact collection (top-tier winners only)

If the user's intent does not clearly map to one of the above, ask which they meant before responding — do not invent a freeform format.

Pre-flight

Read ../okx-agentic-wallet/_shared/preflight.md. If missing, read _shared/preflight.md.

Cross-skill routing on common errors:

  • not logged in → walk the user through the okx-agentic-wallet login flow (run onchainos wallet login), then retry the original action.
  • Backend status codes (--status filter / status / joinStatus / rewardStatus) and error code messages (11002 / 11003 / 11008 / 1860402 / address limit reached / Sui-chain / region-blocked / not eligible): see references/cli-reference.md.

Command Index

All MCP tools mirror the CLI; MCP variants accept activity_name (server-resolves the id) and auto-resolve accountId / wallet addresses from the active session. Full flag tables and return shapes: references/cli-reference.md.

#CommandAuthDescription
1onchainos competition list [--status 0|1|2] [--page-size N] [--page-num N]NoneList competitions (default status=0, active only)
2onchainos competition detail --activity-id <id>NoneRules, prize pool, chain, timeline
3onchainos competition rank --activity-id <id> [--wallet <addr>] --sort-type <type> [--limit N]NoneLeaderboard + user rank. See references/rank.md for self/cross-user semantics and sort-type discovery.
4onchainos competition user-status [--activity-id <id>]Wallet loginParticipation & reward status (omit --activity-id for all activities)
5onchainos competition join --activity-id <id> --evm-wallet <addr> --sol-wallet <addr> --chain-index <chain_id>Wallet loginRegister the active account for the competition
6onchainos competition claim --activity-id <id> --evm-wallet <addr> --sol-wallet <addr>Wallet loginAtomic claim — signs + broadcasts inside the call. See references/claim.md.
7onchainos competition submit-contact --activity-id <id> --contact-type <Telegram|WeChat|Email|Twitter> --contact-value <text>Wallet loginRecord contact for a top-tier winner; only after a claim with needContact: true. See references/claim.md.

--status (request filter): 0=active, 1=ended, 2=all activityStatus (response field): 3=active, 4=ended — different from the request filter

Show full SKILL.md (464 more words)Show less

Output Rules

Internal-only IDs vs user-facing display. Internal numeric IDs (activityId, chainIndex, accountId) are returned in tool responses on purpose — they are needed to chain calls between tools (e.g. after competition_join, you may need to call competition_detail with the activity id to fill the success template). Keep them in the data layer; never render them in user-visible messages.

Never include any internal id in a message produced for the user — under ANY circumstance, in ANY format. Identify activities to the user EXCLUSIVELY by activityName (or shortName if name is unavailable).

Forbidden user-visible patterns (do NOT produce output like this):

  • Agentic Trading Contest (#107)
  • #106 (agenticwallettest1)
  • Any column, row, or inline reference exposing an activity ID (e.g. competition 107, an ID column, a labeled Activity ID row) — same rule, regardless of label, shape, or language.

Correct user-visible pattern:

  • Agentic Trading Contest
  • When disambiguating two activities with the same name, append chainName (e.g. Agentic Trading Contest (Solana)), never the ID.

Behind the scenes (allowed and expected):

  • Reading activityId from a competition_user_status / competition_join response and passing it to competition_detail to fetch the data needed by a fixed template.
  • Any tool-to-tool chaining via numeric ids — as long as the final user-facing message omits them.

When the user asks to act on a specific activity (e.g. "claim Agentic Trading Contest"), the MCP tools competition_claim / competition_join accept activity_name and resolve the id server-side, so you can also use names directly without doing your own lookup.

Output Language

Render every fixed template in the user's conversation language. The template structure (sections, ordering, numbered items, table column count, placeholder positions, the {supportedChains} placeholder, and the [Disclaimer: ...] block) is fixed and must NOT change. Only the natural-language text inside is translated to the user's language naturally.

Placeholders are never translated. {supportedChains}, {chainName}, {rewardUnit}, {txHash}, {accountName}, etc. are filled with API values verbatim — do not localize them. Chain display names (e.g. Solana, X Layer, Base) come from the canonical id → name mapping and stay as-is in every language.

Pre-Delivery Checklist

Final check before sending — covers the reference-file MUSTs that are easy to skip after a long response. (Rules already covered in earlier sections — internal IDs, participateChainIds, *Formatted, language/template fidelity — are not repeated here; verify them by following the rules at their home sections.)

  • On a successful registration response → the [Disclaimer: Digital asset trading involves risk. ...] line is present on its own line at the end. (→ participation.md → Successful registration)
  • On a claim runtime failure (signing / broadcast / network) → the 3-bullet failure-suggestion block is appended. On a pre-check rejection (rewardStatus 0/2/3/4, code 11002, code 11008) → the suggestion block is OMITTED. (→ claim.md → Fixed failure-suggestion block)
  • Before invoking competition_claim → the pre-claim preview line (You are about to claim {rewardAmount} {rewardUnit} on {chainName}. Reply "confirm" to proceed.) was rendered and the user replied with an explicit confirmation. (→ claim.md → Pre-claim preview)

© internet-court, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (references) in vendored/okx/okx-growth-competition of internet-court/internet-court-skill.

  • SKILL.md
  • LICENSE
  • references/claim.md
  • references/cli-reference.md
  • references/details.md
  • references/participation.md
  • references/rank.md

Open the folder on GitHubat commit fa89195

Used in 2 other repositories

We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in internet-court/internet-court-skill, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Okx Growth Competition next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Okx Growth Competition compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Okx Growth Competition this skillinternet-court/internet-court-skill6.6k2 repos~3kAutomated safety check: PassMIT
Social Media IntelligenceHKUDS/Vibe-Trading35k—~10kAutomated safety check: NotesMIT
Signalsalsk1992/CloddsBot3k—~720Automated safety check: PassMIT
Media WritershareAI-lab/lab-skills315—~870Automated safety check: PassApache-2.0
Claude To Imop7418/Claude-to-IM-skill2.9k—~3.4kAutomated safety check: NotesMIT
Tradingview MCPatilaahmettaner/tradingview-mcp5k—~1.3kAutomated safety check: PassMIT

Similar skills

  • Social Media Intelligence

    HKUDS/Vibe-Trading

    Social media intelligence: financial signal extraction from Twitter/X, Telegram, Discord, and Reddit for sentiment-driven trading strategies.

    35k GitHub stars~10k tokensUpdated today
    Business, Finance & HRAuto-check: notes
  • Signals

    alsk1992/CloddsBot

    Signal trading - RSS, Twitter, Telegram triggers to trades. An agent skill from alsk1992/CloddsBot.

    3k GitHub stars~720 tokensUpdated 8 days ago
    Backend & APIsAuto-check passed
  • Media Writer

    shareAI-lab/lab-skills

    Create platform-native content that resonates with each community's culture.

    315 GitHub stars~870 tokensUpdated 25 days ago
    Productivity & AutomationAuto-check passed
  • Claude To Im

    op7418/Claude-to-IM-skill

    Bridge THIS Claude Code or Codex session to Telegram, Discord, Feishu/Lark, QQ, or WeChat so the user can chat with Claude from their phone.

    2.9k GitHub stars~3.4k tokensUpdated 6 mo ago
    Productivity & AutomationAuto-check: notes
  • Tradingview MCP

    atilaahmettaner/tradingview-mcp

    AI Trading Intelligence — live prices, 30+ technical indicators, backtesting (6 strategies), walk-forward overfitting detection, trade logs, equity curves, licensed news sentiment (Marketaux), and…

    5k GitHub stars~1.3k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed
  • Yichen Mac Wechat Dual Open

    mcncarl/yichen-skills

    Create, inspect, repair, and polish a second WeChat app on macOS by copying WeChat, changing the bundle identifier, ad-hoc re-signing, preparing it for the user to open manually, setting Chinese…

    4.4k GitHub stars~1.5k tokensUpdated 7 days ago
    Productivity & AutomationAuto-check passed

More from internet-court/internet-court-skill

All 80 skills in this repo
  • Kleros IPFS Upload

    internet-court/internet-court-skill

    Uploads one Kleros-related file per paid request to IPFS through the Kleros x402 gateway for 0.01 USDC on Base, returning a CID that Kleros contracts can reference.

    6.6k GitHub stars~4.9k tokensUpdated 1 mo ago
    Auto-check: notes
  • 0G Compute Network Guide

    internet-court/internet-court-skill

    Guides building on the 0G Compute Network, a decentralized GPU marketplace for AI inference and fine-tuning, with SDK patterns and CLI commands.

    6.6k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • PNP Prediction Markets on Solana

    internet-court/internet-court-skill

    Creates, trades and settles permissionless prediction markets on Solana with any SPL token as collateral, including social-media and custom-oracle markets.

    6.6k GitHub stars~7.5k tokensUpdated 1 mo ago
    Auto-check: notes
  • BNB Chain MCP Server

    internet-court/internet-court-skill

    Connects an agent to the BNB Chain MCP server to read blocks and contracts, move tokens and NFTs, register ERC-8004 agents and use Greenfield storage.

    6.6k GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed
  • GenLayer ERC-7710 Connector

    internet-court/internet-court-skill

    Specifies how a GenLayer Intelligent Contract decision about an agent's performance becomes an ERC-7710 revocation or policy change, through a relayer or bridge and an EVM controller.

    6.6k GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed
  • GenLayer Agent Supervision Adapter

    internet-court/internet-court-skill

    Specifies how a GenLayer Intelligent Contract should supervise an AI agent, with review rubrics, evidence schemas and continue, warn, constrain or revoke decisions.

    6.6k GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed

Questions about Okx Growth Competition

What does Okx Growth Competition do?

List OKX Agentic Wallet exclusive trading competitions, register users for contests, track participation and leaderboard rankings, and claim won rewards. Okx Growth Competition is an agent skill from internet-court/internet-court-skill. List OKX Agentic Wallet exclusive trading competitions, register users for contests, track participation and leaderboard rankings, and claim won rewards.

When should I use Okx Growth Competition?

Okx Growth Competition fits situations like: users want to list available trading competitions; view competition rules / prize pool / total prizes; check the leaderboard (who is winning); their own rank (am I in the prize zone.

How do I install Okx Growth Competition in Claude Code?

Run `npx skills add internet-court/internet-court-skill --skill okx-growth-competition -a claude-code`. Or copy the skill folder (vendored/okx/okx-growth-competition in internet-court/internet-court-skill) into .claude/skills/okx-growth-competition in your project. Claude Code loads it when a task matches its description.

How do I install Okx Growth Competition in Codex?

Run `npx skills add internet-court/internet-court-skill --skill okx-growth-competition -a codex`. Or copy the skill folder (vendored/okx/okx-growth-competition in internet-court/internet-court-skill) into .agents/skills/okx-growth-competition in your project. Codex loads it when a task matches its description.

Can I use Okx Growth Competition in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add internet-court/internet-court-skill --skill okx-growth-competition -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/okx-growth-competition, .gemini/skills/okx-growth-competition, .github/skills/okx-growth-competition and .opencode/skills/okx-growth-competition in your project.

What does Okx Growth Competition need to run?

SKILL.md names no scripts, command-line tools or credentials: Okx Growth Competition is instructions for the agent only.

Does Okx Growth Competition access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Okx Growth Competition safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Okx Growth Competition use?

Okx Growth Competition is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Okx Growth Competition use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.

What are the alternatives to Okx Growth Competition?

Skills that share tags, products or a category with Okx Growth Competition: Social Media Intelligence (HKUDS/Vibe-Trading, 35k stars), Signals (alsk1992/CloddsBot, 3k stars), Media Writer (shareAI-lab/lab-skills, 315 stars) and Claude To Im (op7418/Claude-to-IM-skill, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Okx Growth Competition?

internet-court (a GitHub organization) maintains it in internet-court/internet-court-skill, which has 6,551 GitHub stars. The repository holds 80 skills in this directory. The repository was last updated on August 19, 2026.

Source: internet-court/internet-court-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.