Okx Activity
Register for the OKX.AI Trading Hackathon or explain its entry requirements and...
Install
npx skills add internet-court/internet-court-skill --skill okx-activity -g -a claude-code -y- Repository
- internet-court/internet-court-skill7k
- Category
- Engineering
- Updated
- 9d ago
- License
- MIT
- Context cost
- Lightabout 1,184 tokens
- Runs scripts
- No, instructions only
What it does
Register for the OKX.AI Trading Hackathon or explain its entry requirements and eligibility. Trigger on requests in any language to register, sign up, join, enter, or participate in the hackathon. Registers an existing Trading ASP; never creates one.
OKX Activity, registration & participation for OKX campaign activities
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.
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.
Intent Routing
| User Intent | Activity | Reference |
|---|---|---|
| Register, sign up, join, enter, or participate in the hackathon, in any language | OKX.AI Trading Hackathon | hackathon-core.md, then hackathon-registration.md |
| Hackathon entry requirements or eligibility, in any language, 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.
