Skills okx-growth-competition

📦

okx-growth-competition

Name: okx-growth-competition
Author: internet-court

v4.2.1 Content revision r1 High Risk 📁 Filesystem access🌐 Network access⚙️ External commands

Manage OKX Trading Competitions

Trading competition workflows require status checks, wallet context, and fixed response templates. This skill guides Claude, Codex, and Claude Code through OKX competition discovery, registration, ranking, reward claims, and contact follow-up.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "okx-growth-competition" from https://skillstore.io/skills/internet-court-okx-growth-competition.md and its manifest at https://skillstore.io/api/skills/internet-court-okx-growth-competition/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/internet-court-okx-growth-competition.md Signed manifest GET /api/skills/internet-court-okx-growth-competition/manifest Signed lockfile GET /api/skills/internet-court-okx-growth-competition/lockfile

Test it

Using "okx-growth-competition". Show available competitions.

Expected outcome:

The skill returns active and ended competition tables with name, supported chains, time, prize pool, and OKX detail links.

Using "okx-growth-competition". Did I win Agentic Trading Contest?

Expected outcome:

The skill reports join status, reward status, reward amount when available, and whether a claim is currently possible.

Using "okx-growth-competition". Claim my reward for Agentic Trading Contest.

Expected outcome:

The skill previews the reward amount and chain, asks for explicit confirmation, then reports the claim result and transaction hash.

Security Audit

High Risk

v2 • 7/21/2026 Open versioned report

All 103 static findings are false positives caused by Markdown, fixed relative references, field names, URLs, and documented CLI syntax. The skill nevertheless directs an agent to execute irreversible blockchain reward claims and to collect optional delivery contact details. These actions require strong platform-enforced consent and data-handling controls.

Files scanned

972

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (2)

High

references/claim.md:39-56 SKILL.md:91-94

On-Chain Claim Transaction Execution

The documented claim flow signs and broadcasts a blockchain transaction through a wallet session. The flow requests explicit confirmation, but a successful call has financial and irreversible effects.

The documentation explicitly states that the claim tool signs and broadcasts on-chain, and it describes the operation as atomic.

Medium

references/claim.md:89-114 references/claim.md:116-143

Optional Contact Information Collection

After a qualifying claim, the skill asks users to submit Telegram, WeChat, email, or Twitter contact information for merchandise delivery. This introduces third-party personal-data handling despite the stated optional prompt.

The documented flow explicitly parses, validates, and submits a contact value to a backend service.

Risk Factors

📁 Filesystem access (8)

references/claim.md:3 references/claim.md:54 references/details.md:3 references/participation.md:3 references/participation.md:9 references/participation.md:57 references/rank.md:3 SKILL.md:76

🌐 Network access (2)

references/cli-reference.md:150 SKILL.md:8

⚙️ External commands (50)

Audited by: claude View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/internet-court-okx-growth-competition/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/internet-court-okx-growth-competition/security.svg)](https://skillstore.io/skills/internet-court-okx-growth-competition?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/internet-court-okx-growth-competition?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/internet-court-okx-growth-competition/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/internet-court-okx-growth-competition.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

internet-court. (2026). okx-growth-competition security audit report (audit version 2) [Author version 4.2.1]. Skillstore. https://skillstore.io/skills/internet-court-okx-growth-competition/audits/2

BibTeX citation

@techreport{internet-court-internet-court-okx-growth-competition-2026,
  author = {internet-court},
  title = {okx-growth-competition security audit report (audit version 2)},
  institution = {Skillstore},
  year = {2026},
  number = {2},
  url = {https://skillstore.io/skills/internet-court-okx-growth-competition/audits/2},
  note = {Author version 4.2.1}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "okx-growth-competition security audit report (audit version 2)"
version: "4.2.1"
type: report
authors:
  - name: "internet-court"
date-released: "2026-07-21"
url: "https://skillstore.io/skills/internet-court-okx-growth-competition/audits/2"
identifiers:
  - type: other
    value: "skillstore:internet-court-okx-growth-competition:audit:2"
    description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Higher Skillstore usage

Author / source Skillstore Score Evidence Confidence Skillstore usage Updated

internet-court Recommended Current

internet-court-okx-growth-competition

Skillstore Score 38

Evidence Confidence Medium

Skillstore usage 4

Updated

2026-08-21

okx

okx-okx-growth-competition

Skillstore Score 38

Evidence Confidence Medium

Skillstore usage 1

Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Compare Competitions

Review active and ended competitions before choosing where to participate.

Track Ranking and Rewards

Check leaderboard positions, prize-zone status, and reward eligibility across every leaderboard.

Resolve Registration Status

Explain duplicate registration, registered wallet, region limits, and claim status errors.

Try These Prompts

List Competitions

Show me all OKX Agentic Wallet trading competitions and separate active ones from ended ones.

Explain Rules

Show the rules, supported chains, timeline, and prize pool for [competition name].

Check My Standing

Check my rank and reward status for [competition name] across every leaderboard.

Claim With Contact Follow-up

For [competition name], check my reward status. If I can claim, preview the amount and chain, wait for my confirmation, then guide any required winner contact submission.

Best Practices

Review competition detail data before registration so chain and prize rules are clear.
Confirm every claim, swap, or contact submission with the user before calling a tool.
Use activity names in user messages and keep internal IDs out of final replies.

Avoid

Do not claim rewards, execute swaps, or submit contacts without explicit user confirmation.
Do not treat the claim chain and trading-chain set as the same field.
Do not expose activityId, chainIndex, or accountId in user-visible output.