trading-futures

Automate perpetual futures trading across Binance, Bybit, Hyperliquid, and MEXC via CLI.

71|22|Updated Apr 6, 2020
One-click install
npx skills add https://github.com/nirholas/agenti --skill trading-futures-nirholas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trading-futures
Source: https://github.com/nirholas/agenti/tree/main/packages/protocols/x402-cloddsbot/src/skills/bundled/trading-futures
Command: npx skills add https://github.com/nirholas/agenti --skill trading-futures-nirholas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables automated, cross-exchange perpetual futures trading from a single CLI, reducing manual setup and monitoring overhead across multiple platforms.

Core Features & Use Cases

  • Multi-exchange futures trading from Binance, Bybit, Hyperliquid, and MEXC via a unified CLI interface.
  • Support for common order types (market, limit, stop) with per-exchange leverage and risk controls.
  • CLI-driven account overview, positions, funding, markets, orders, and history for day-to-day trading operations.
  • Example use case: a developer opens a long position on BTCUSDT across configured exchanges and tracks PnL and exposure from one place.

Quick Start

Launch the Futures CLI and start executing trades across Binance, Bybit, Hyperliquid, and MEXC using configured API keys.

Frequently Asked Questions about trading-futures

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

FAQPage Schema
How do I automate perpetual futures trading across multiple exchanges from a single CLI?

Automating perpetual futures trading across Binance, Bybit, Hyperliquid, and MEXC is achieved through a unified CLI that manages leverage, orders, funding, and risk controls. It uses env-based authentication gates to execute trades and monitor account positions from one interface.

Can I manage cross-exchange futures positions and funding rates through a command line interface?

Managing cross-exchange futures positions and funding rates is supported via CLI-driven commands. The interface provides a unified account overview, allowing developers to track markets, execute orders, and monitor funding across Binance, Bybit, Hyperliquid, and MEXC.

What is the best way to configure API keys for automated crypto futures trading workflows?

Configuring API keys for automated crypto futures trading workflows requires setting up env-based authentication gates. This robust error handling approach secures your exchange clients for Binance, Bybit, Hyperliquid, and MEXC before executing CLI operations.

Does this multi-exchange futures CLI support market, limit, and stop orders with leverage controls?

This multi-exchange futures CLI supports common order types including market, limit, and stop orders. It integrates per-exchange leverage and risk controls, enabling developers to open positions and track PnL exposure across configured platforms.

How do I check my perpetual futures PnL and open positions across Binance, Bybit, and MEXC?

Checking perpetual futures PnL and open positions across Binance, Bybit, and MEXC is done through CLI-driven account overview commands. These commands retrieve day-to-day trading operations data, including history and exposure, from the integrated exchange clients.

What are the limitations of using a CLI for cross-exchange perpetual futures automation?

Limitations of using a CLI for cross-exchange perpetual futures automation include relying on env-based authentication and robust error handling to manage API failures. It requires developer knowledge to parse commands and integrate risk controls across Binance, Bybit, Hyperliquid, and MEXC.