okx-activity

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

OKX Activity — registration & participation for OKX campaign activities

OKX活动——OKX营销活动的报名与参与

Each activity's flow, CLI reference, FAQ, and gates live in this skill's

references/

behind an

<activity>-*.md

prefix. This SKILL.md routes only — no templates, no CLI flags, no per-activity copy — so adding an activity never changes the rules of an existing one.

每个活动的流程、CLI参考文档、常见问题及校验规则都存放在本技能的

references/

目录下，以

<activity>-*.md

为前缀命名。本SKILL.md仅负责路由——不包含模板、CLI参数或特定活动文案——因此新增活动不会改变现有活动的规则。

Pre-flight Checks

前期检查

Before your first onchainos command, read

../okx-agentic-wallet/_shared/preflight.md

once. If it does not exist, read

_shared/preflight.md

instead.

BLOCKING — it runs before the first

onchainos

command of the session, for every activity, a read-only listing call included.

在执行第一条onchainos命令前，请先阅读

../okx-agentic-wallet/_shared/preflight.md

一次。若该文件不存在，则阅读

_shared/preflight.md

。

强制要求——在会话中执行第一条

onchainos

命令前，无论是什么活动（包括只读列表查询），都必须先完成此检查。

Intent Routing

意图路由

User Intent	Activity	Reference
"register / sign up my ASP for the hackathon" · 报名黑客松 · 参加交易黑客松 · 黑客马拉松	OKX.AI Trading Hackathon	hackathon-core.md, then hackathon-registration.md
hackathon entry requirements / eligibility / 报名条件 / 参赛资格 — not mid-registration	OKX.AI Trading Hackathon	hackathon-core.md, then hackathon-faq.md

Before producing ANY user-facing message about an activity, that activity's
*-core.md
must be loaded (BLOCKING). It carries that activity's gates, output rules, and send-gate — the flow and FAQ files do not repeat them, so opening a

-registration.md

-faq.md

first is not a shortcut, it is a skipped gate. Do not improvise a flow, template, or eligibility answer from this file, from memory, or from the CLI's

--help

output alone.

If the request names an activity with no row above (no reference file exists for it), say that activity isn't supported by this skill yet — never adapt another activity's flow to it, and never guess a CLI subcommand for it.

用户意图	活动	参考文档
"为我的ASP注册黑客松"·报名黑客松·参加交易黑客松·黑客马拉松	OKX.AI Trading Hackathon	hackathon-core.md，随后是hackathon-registration.md
黑客松报名条件/参赛资格——非报名过程中询问	OKX.AI Trading Hackathon	hackathon-core.md，随后是hackathon-faq.md

在生成任何与活动相关的用户可见信息前，必须先加载该活动的
*-core.md
文件（强制要求）。该文件包含活动的校验规则、输出规则和发送限制——流程和FAQ文件不会重复这些内容，因此直接打开

-registration.md

或

-faq.md

并非捷径，而是跳过了校验步骤。请勿根据本文件、记忆或CLI的

--help

输出自行编造流程、模板或资格答案。

如果用户请求的活动在上述表格中没有对应行（即不存在对应的参考文件），请告知用户该活动暂不被本技能支持——切勿套用其他活动的流程，也不要猜测对应的CLI子命令。

Command Index

命令索引

This skill drives

onchainos <activity>

subcommands (hackathon →

onchainos hackathon

). Learn exact syntax from the CLI, not from memory: run

onchainos hackathon --help

for the subcommand list, and

onchainos hackathon <subcommand> --help

for a subcommand's flags. Full parameter tables, return-field schemas, and worked examples live in hackathon-registration.md.

本技能驱动

onchainos <activity>

子命令（黑客松对应

onchainos hackathon

）。**请从CLI中学习准确的语法，不要凭记忆：**运行

onchainos hackathon --help

查看子命令列表，运行

onchainos hackathon <subcommand> --help

查看子命令的参数。完整的参数表、返回字段 schema 和示例请查看hackathon-registration.md。

Wrong-skill guard

技能区分防护

An activity here enters the subject that activity defines (hackathon → an existing Trading ASP agent).

competition join

(

okx-growth-competition

) signs the wallet account up for a standard trading competition. Different systems, different subjects — NEVER: substitute one for the other, because the two register different things and neither call can be undone.

If one request carries signals for both (e.g. names "hackathon"/"黑客松" and "competition"/"大赛"/"cup"), ask which the user means before running any command.

本技能中的活动针对该活动定义的主体进行操作（黑客松对应已有的Trading ASP agent）。

competition join

（

okx-growth-competition

技能）是为钱包账户报名标准交易大赛。两者属于不同系统，操作主体不同——绝对禁止：相互替代，因为两者注册的对象不同，且操作均不可撤销。

如果用户的请求同时包含两种活动的信号（例如同时提到“hackathon”/“黑客松”和“competition”/“大赛”/“杯”），请先询问用户具体指的是哪一个，再执行任何命令。

Security

安全规则

Every activity registration is irreversible — there is no list, update, status, or undo subcommand. MUST: hold an explicit confirm reply from the user before submitting; never answer the confirmation prompt on their behalf, and never treat a one-shot request that already named the subject as having pre-answered it. The full gate lives in the activity's
```
-registration.md
```
.
NEVER: log, print, or pass the JWT in a flag — it is injected by the client layer from the keychain, so leaking it would let an attacker act as the user. Activity flows create no new secrets.
MUST: mask user identifiers (OKX UID and the like) when echoing the executed command (
```
--uid <hidden>
```
) — they are never returned by the CLI and never pasted raw into the conversation.
NEVER: identify an activity by its internal activity id, in any format — name it. The CLI does not return that id; do not source it from anywhere else.
Creating an agent identity is never part of an activity flow — that is
```
okx-ai
```
. This skill only enters subjects that already exist.

所有活动报名均不可撤销——不存在列表、更新、状态查询或撤销子命令。必须：在提交前获取用户明确的确认回复；切勿代用户回复确认提示，也不要将一次性提及活动主体的请求视为已预先确认。完整的校验规则请查看活动的
```
-registration.md
```
文件。
绝对禁止：记录、打印或在参数中传递JWT——它由客户端层从密钥链注入，泄露会导致攻击者冒充用户身份。活动流程不会生成新的密钥。
必须：在回显已执行的命令时隐藏用户标识符（如OKX UID），格式为
```
--uid <hidden>
```
——CLI不会返回这些标识符，也不要在对话中直接粘贴原始内容。
绝对禁止：以任何格式使用活动内部ID来标识活动——请使用活动名称。CLI不会返回该ID，也不要从其他来源获取。
创建agent身份不属于活动流程的一部分——这是
```
okx-ai
```
技能的功能。本技能仅针对已存在的主体进行操作。

Global Notes

全局说明

Reply in the user's language. Every template in this skill's references is authored in English as a structure guide — translate it before sending, keeping the layout and fields unchanged and every URL byte-for-byte, still a link.
Each activity's
```
-core.md
```
owns its own gates, Output Rules, and Pre-Delivery Checklist; those are additional to this file, never a substitute for it.

使用用户的语言回复。本技能参考文档中的所有模板均以英文编写，作为结构指南——发送前需翻译成用户使用的语言，保持布局和字段不变，所有URL需完整保留为链接。
每个活动的
```
-core.md
```
文件独立管理其校验规则、输出规则和交付前检查清单；这些内容是对本文件的补充，而非替代。

Adding an activity (maintainers)

新增活动（维护人员指南）

Add
```
references/<activity>-core.md
```
— its gates, reading order, output rules, and pre-delivery checklist — plus
```
references/<activity>-*.md
```
for the flow and FAQ.
Add one Intent Routing row per user intent that activity serves, each a complete markdown link.
Extend this file's
```
description
```
with the new activity's triggers.

添加
```
references/<activity>-core.md
```
文件——包含活动的校验规则、阅读顺序、输出规则和交付前检查清单——以及对应活动流程和FAQ的
```
references/<activity>-*.md
```
文件。
为该活动支持的每个用户意图添加一行意图路由，每行需包含完整的markdown链接。
在本文件的
```
description
```
中添加新活动的触发条件。