ccxt_skill

This skill helps you develop and debug ccxt integrations across exchanges, APIs, order management, and market data with practical guidance.
  • Python

10.3k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill 2025emma/vibe-coding-cn --skill ccxt

  • SKILL.md17.4 KB

Overview

This skill provides practical guidance for using CCXT, the multi-language cryptocurrency trading library for exchange APIs, market data, orders, and automation across 150+ exchanges. It focuses on common patterns, options, and pitfalls developers face when integrating trading, spot, margin, and derivatives features. Use it to accelerate reliable integrations and troubleshoot typical issues without risking funds.

How this skill works

The skill inspects CCXT usage patterns, common configuration flags, and method behaviors (createOrder, market buys, conditional orders, reduceOnly, funding rates, etc.). It explains how CCXT maps unified methods to exchange-specific endpoints, how feature flags and options affect behavior, and what debugging output to collect. It also highlights recommended parameters, error-reporting steps, and where to check exchange capabilities (exchange.has and exchange.features).

When to use it

  • Integrating a new exchange or building cross-exchange tooling
  • Placing, canceling, or managing spot, margin, and futures orders programmatically
  • Debugging unexpected order behavior or API errors
  • Designing automated trading strategies or backtesting connectors
  • Checking whether an exchange supports specific order types or features

Best practices

  • Always call await exchange.loadMarkets() before trading to populate market metadata
  • Enable verbose logging (exchange.verbose = true) when debugging and include full request/response output
  • Report issues with a minimal reproducible snippet, CCXT version, language/runtime version, exchange, and full stacktrace
  • Check exchange.has and exchange.features for support of specialized methods (e.g., createMarketBuyOrderWithCost, createStopLossOrder) rather than assuming behavior
  • Never post API keys or secrets; redact credentials from any shared logs

Example use cases

  • Place a spot market buy considering createMarketBuyRequiresPrice or use createMarketBuyOrderWithCost when supported
  • Create reduceOnly orders for closing positions on derivatives markets using params={'reduceOnly': True}
  • Attach takeProfit and stopLoss to a position when the exchange supports attached orders, otherwise submit separate conditional orders
  • Load and inspect market contractSize for perp/swap symbols before sizing orders
  • Collect verbose exchange requests/responses to debug mismatched results or unexpected error codes

FAQ

Enable exchange.verbose = true, run the minimal reproducible script, and capture both request and response text plus the full traceback. Share language, CCXT version, exchange name, method, and code snippet (no keys).

Does CCXT guarantee feature parity across exchanges?

No. CCXT provides a unified interface but feature availability varies. Check exchange.has and exchange.features and consult the exchange-specific implementation if you need exact endpoint details.

How do I place a market buy by quote currency (cost)?

If the exchange supports it, use createMarketBuyOrderWithCost or set exchange.options['createMarketBuyOrderRequiresPrice']=False to treat amount as cost. Otherwise provide price to compute cost from base amount.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
ccxt skill by 2025emma/vibe-coding-cn | VeilStrat