Agent skill · software engineering · ccxt
new-exchange
Scaffold a new CCXT exchange integration in TypeScript, following the certified-exchange template. Walks through describe(), required unified methods, parsers, capability flags, sandbox setup, and static fixtures. Use when adding support for an exchange that does not exist yet under ts/src/.
Why this skill is useful
Adds a complete scaffold for new CCXT exchange integrations, including specific TypeScript structure and required methods that the AI wouldn't generate on its own.
What it needs
About 7k tokens when loaded. Last updated 2026-08-06. 43,551 stars on the source repository.
What this skill does
New Exchange Integration Scaffold a new exchange in ts/src/<id>.ts (REST) and optionally ts/src/pro/<id>.ts (WebSocket). Read first: wiki/Requirements.md (mandatory unified methods) and CONTRIBUTING.md (transpiler rules). The CCXT root CLAUDE.md is the contributor guide. Inputs <id>: lowercase exchange id, no separators (e.g. mynewex) <Name>: human-readable name (e.g. My New Exchange) API docs URL(s) Whether the exchange has a testnet/sandbox Step 1 — Pick a reference exchange Don't write from scratch. Copy a similar exchange that's already certified and adapt it. Style Reference --- --- Spot + futures, signed REST ts/src/binance.ts, ts/src/okx.ts Spot only ts/src/kraken.ts, ts/src/coinbase.ts Derivatives focus ts/src/bybit.ts, ts/src/bitmex.ts Decentralised / on-chain signing ts/src/hyperliquid.ts, ts/src/dydx.ts WebSocket reference ts/src/pro/binance.ts, ts/src/pro/okx.ts Open the reference next to your new file and pattern-match — never invent new conventions. Step 2 — Create ts/src/<id>.ts Skeleton: Step 3 — Define implicit API methods URLs in the api block become methods automatically: 'symbols' → this.publicGetSymbols(params) 'ticker/{pair}' → this.publicGetTickerPair({ pair: market['id'] }) 'orders' under private.get → this.privateGetOrders(params) Don't write explicit HTTP wrappers. After listing the URL in api, run npm run emitAPITs to regenerate ts/src/abstract/<id>.ts (the auto-typed declarations). Step 4 — Docstrings on every public method Every public method needs a JSDoc block. The transpilers convert it to native docstrings in Python/PHP/C#/Go, and npm run build-docs produces wiki entries from them. Pattern: Rules: lowercase @description, @param {object} [params] always present, document every params.<key> you read in the body, link @returns to the manual structure. See CLAUDE.md §7 for the full ruleset. Step 5 — Required parsers For every fetch method, write a matching parser. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills ccxt/new-exchange