OKX Exchange WebSocket Skill
PassAudited by ClawScan on May 1, 2026.
Overview
This is a coherent public OKX market-data WebSocket skill; it starts network subscriptions and writes local output, but those behaviors are disclosed and purpose-aligned.
Before installing, make sure you trust the local `uxc` binary, understand that subscriptions may keep running until stopped, and monitor the NDJSON sink files so they do not grow unexpectedly.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Running the command can start a live market-data feed and create or grow a local NDJSON file.
The skill instructs use of an external CLI to open a WebSocket connection and write output to a local file. This is the advertised function and is scoped to public OKX data, but it is still tool execution with file output.
Core Workflow: `uxc subscribe start wss://ws.okx.com:8443/ws/v5/public --transport websocket --init-frame ... --sink file:$HOME/.uxc/subscriptions/okx-btcusdt-ticker.ndjson`
Run it only for intended public channels, verify the endpoint and subscribe frame, and choose a sink path you are comfortable writing to.
A subscription left running could keep a network connection open and continue growing the output file.
The documented stop step indicates that subscription jobs can continue after being started. The persistence is disclosed and aligned with streaming WebSocket data.
Stop the job when finished: `uxc subscribe stop <job_id>`
Use `uxc subscribe list`, `uxc subscribe status`, and `uxc subscribe stop` to monitor and stop jobs when they are no longer needed.
The behavior depends on whichever `uxc` binary is installed locally.
The skill depends on an external `uxc` runtime, while the provided registry metadata declares no required binaries or install spec. Users must independently trust and manage that dependency.
Prerequisites: - `uxc` is installed and available in `PATH`.
Install `uxc` from a trusted source and consider declaring it in the skill metadata for clearer dependency review.