Okx Dex Signal
Wire your agent to OKX OnchainOS CLI flows for DEX signal and on-chain operations with shared chain resolution and session pre-flight checks.
Overview
OKX DEX Signal is an agent skill for the Build phase that integrates the OKX OnchainOS CLI for DEX signal and on-chain operations with shared chain resolution and release pre-flight checks.
Install
npx skills add https://github.com/okx/onchainos-skills --skill okx-dex-signalWhat is this skill?
- Shares OnchainOS chain name resolution across skills (e.g., ethereum, base, solana, xlayer)
- Documents six chains with wallet address creation and chainIndex mapping table
- Session pre-flight: fetch latest GitHub release tag via API before first `onchainos` command
- Fallback path when release API fails but a local binary already exists
- Wallet supports 17+ chains beyond the six address-creation chains—`onchainos wallet chains` for full list
- 6 chains listed with wallet address creation support in shared chain table
- 17+ chains supported for wallet interaction beyond the six creation chains
Adoption & trust: 5k installs on skills.sh; 284 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want an agent to run OKX on-chain commands but chain names, wallet support, and CLI version drift cause failed or unsafe first commands each session.
Who is it for?
Indie builders prototyping crypto agents that already use OnchainOS and need consistent chain tables and install discipline across skills.
Skip if: Non-crypto SaaS products, builders who cannot allow network/shell access, or anyone seeking investment advice without reviewing keys and chain risk themselves.
When should I use this skill?
Before running OnchainOS DEX signal or related CLI commands in a session, after resolving chains and latest release per shared pre-flight docs.
What do I get? / Deliverables
The agent resolves chains correctly, runs documented pre-flight release checks, and invokes `onchainos` for DEX signal workflows with the shared onchainos-skills conventions.
- Version-checked `onchainos` session ready for DEX signal commands
- Chain-resolved CLI invocations aligned with shared onchainos-skills docs
Recommended Skills
Journey fit
OnchainOS skills are integration packages you install while building wallet- or trading-adjacent agent features, before you ship hardened production ops. okx-dex-signal sits in integrations because it connects to external OKX onchain tooling and chain indexes rather than owning your app’s core backend logic.
How it compares
Skill-pack integration around the OnchainOS CLI—not a hosted MCP dashboard or a generic REST API wrapper alone.
Common Questions / FAQ
Who is okx-dex-signal for?
Solo developers building agent-driven on-chain tooling on OKX OnchainOS who need DEX signal flows plus the shared chain and pre-flight conventions.
When should I use okx-dex-signal?
Use it during build integrations when you are wiring OnchainOS CLI commands for DEX signals, wallet chains, or related onchainos-skills automation in a fresh agent session.
Is okx-dex-signal safe to install?
It implies shell, network, and likely wallet secrets; review the Security Audits panel on this page and never grant mainnet keys without your own threat model.
SKILL.md
READMESKILL.md - Okx Dex Signal
# Shared Chain Name Support > This file is shared across all onchainos skills. The CLI accepts human-readable chain names and resolves them automatically. The following 6 chains support **wallet address creation** (i.e., you can generate a wallet address on these chains): | Chain | Name | chainIndex | |---|---|---| | XLayer | `xlayer` | `196` | | Solana | `solana` | `501` | | Ethereum | `ethereum` | `1` | | Base | `base` | `8453` | | BSC | `bsc` | `56` | | Arbitrum | `arbitrum` | `42161` | > **Note**: The wallet supports interacting with 17+ chains beyond this list (e.g., Polygon, Avalanche, Optimism). > Run `onchainos wallet chains` for the full list of supported chains. # Shared Pre-flight Checks > This file is shared across all onchainos skills. Follow these steps before the first `onchainos` command each session. Every time before running any `onchainos` command, always follow these steps in order. Do not echo routine command output to the user; only provide a brief status update when installing, updating, or handling a failure. 1. **Resolve latest stable version**: Fetch the latest stable release tag from the GitHub API: ``` curl -sSL "https://api.github.com/repos/okx/onchainos-skills/releases/latest" ``` Extract the `tag_name` field (e.g., `v1.0.5`) into `LATEST_TAG`. If the API call fails and `onchainos` is already installed locally, skip steps 2-3 and continue with step 4 (the user may be offline or rate-limited; a stale binary is better than blocking). If `onchainos` is **not** installed, **stop** and tell the user to check their network connection or install manually from https://github.com/okx/onchainos-skills. 2. **Install or update**: If `onchainos` is not found, or if the cache at `~/.onchainos/last_check` (`$env:USERPROFILE\.onchainos\last_check` on Windows) is older than 12 hours: - Download the installer and its checksum file from the latest release tag: - **macOS/Linux**: `curl -sSL "https://raw.githubusercontent.com/okx/onchainos-skills/${LATEST_TAG}/install.sh" -o /tmp/onchainos-install.sh` `curl -sSL "https://github.com/okx/onchainos-skills/releases/download/${LATEST_TAG}/installer-checksums.txt" -o /tmp/installer-checksums.txt` - **Windows**: `Invoke-WebRequest -Uri "https://raw.githubusercontent.com/okx/onchainos-skills/${LATEST_TAG}/install.ps1" -OutFile "$env:TEMP\onchainos-install.ps1"` `Invoke-WebRequest -Uri "https://github.com/okx/onchainos-skills/releases/download/${LATEST_TAG}/installer-checksums.txt" -OutFile "$env:TEMP\installer-checksums.txt"` - Verify the installer's SHA256 against `installer-checksums.txt`. On mismatch, **stop** and warn — the installer may have been tampered with. - Execute: `sh /tmp/onchainos-install.sh` (or `& "$env:TEMP\onchainos-install.ps1"` on Windows). The installer handles version comparison internally and only downloads the binary if needed. - On other failures, point to https://github.com/okx/onchainos-skills. 3. **Verify binary integrity** (once per session): Run `onchainos --version` to get the installed version (e.g., `1.0.5` or `2.0.0-beta.0`). Construct the installed tag as `v<version>`. Download `checksums.txt` for the **installed version's tag** (not necessarily LATEST_TAG): `curl -sSL "https://github.com/okx/onchainos-skills/releases/download/v<version>/checksums.txt" -o /tmp/onchainos-checksums.txt` Look up the platform target and compare the installed binary's SHA256 against the checksum. On mismatch, reinstall (step 2) and re-verify. If still mismatched, **stop** and warn. - Platform targets — macOS: `arm64`->`aarch64-apple-darwin`, `x86_64`->`x86_64-apple-darwin`; Linux: `x86_64`->`x86_64-unknown-linux-gnu`, `aarch64`->`aarch64-unknown-linux-gnu`, `i686`->`i686-unknown-linux-gnu`, `armv7l`->`armv7-unknown-linux-gnueabihf`; Windows: `AMD64`->`x86_64-pc-windows-msvc`, `x86`->`i686-pc-windows-msvc`, `ARM64`->`aarch64-pc-windows-msvc` - Hash c