exchange-adapters

Normalize cryptocurrency exchange account data into a unified schema.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/kann420/Cross-Arbitrage-Exchange --skill exchange-adapters
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exchange-adapters
Source: https://github.com/kann420/Cross-Arbitrage-Exchange/tree/main/.claude/exchange-adapters
Command: npx skills add https://github.com/kann420/Cross-Arbitrage-Exchange --skill exchange-adapters

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a robust, production-oriented framework for building and maintaining exchange adapter modules, essential for cross-exchange hedge managers. It tackles the complexities of inconsistent exchange data formats, API authentication, and data normalization.

Core Features & Use Cases

  • Unified Data Schema: Normalizes data from multiple exchanges (Binance, OKX) into a consistent internal schema, simplifying downstream processing.
  • Safe Authentication: Implements secure API authentication patterns for exchanges.
  • Data Normalization: Handles symbol mapping, timestamp consistency, and decimal-safe financial calculations.
  • Use Case: A hedge manager needs to track a KITE/USDG spot position on OKX and hedge it with a KITEUSDT perpetual short on Binance. This Skill ensures that both positions are represented with a common canonicalAsset ('KITE') while preserving their distinct exchange-specific details and quote assets.

Quick Start

Use the exchange-adapters skill to fetch balances from Binance and OKX.

Frequently Asked Questions about exchange-adapters

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I normalize crypto exchange data from Binance and OKX into a unified schema?

You can normalize crypto exchange data by using adapter modules that map inconsistent symbols, timestamps, and quote assets from Binance and OKX into a unified internal schema for downstream processing.

How do I handle symbol mapping inconsistencies for cross-exchange hedge tracking?

You handle symbol mapping inconsistencies by assigning a canonicalAsset identifier to unify distinct exchange-specific symbols, ensuring a KITE/USDG spot position and KITEUSDT perpetual short are represented commonly while preserving distinct quote assets.

What is the best way to implement safe API authentication for cryptocurrency exchange adapters?

The best way to implement safe API authentication is by using the framework's standardized secure patterns, ensuring protected connections to exchanges like Binance and OKX for read-only portfolio tracking and PnL inputs.

Can I maintain raw API payloads for audit while normalizing crypto account data?

Yes, you can maintain raw API payloads for audit because the architecture focuses on preserving original exchange responses alongside the normalized balances, holdings, and positions for replay and audit purposes.

Does this framework support decimal-safe financial calculations for crypto positions?

Yes, the framework supports decimal-safe financial calculations by handling timestamp consistency and decimal precision during the data normalization process for portfolio tracking and PnL inputs.