maxxit-lazy-trading_skill

This skill helps you automate perpetual trading on Ostium by managing positions, risk, and market data with Maxxit's Lazy Trading API.
  • Python

2.6k

GitHub Stars

11

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 openclaw/skills --skill maxxit-lazy-trading

  • _meta.json2.2 KB
  • breakout-strategy.py7.0 KB
  • donchian-adx-strategy.py4.7 KB
  • ema-strategy.py4.5 KB
  • mean-reversion-strategy.py7.0 KB
  • README.md2.9 KB
  • rsi-bollinger-strategy.py5.0 KB
  • SKILL.md77.1 KB
  • strategy_common.py25.1 KB
  • taker-strategy.py8.0 KB
  • vwap-strategy.py6.6 KB

Overview

This skill executes perpetual futures trades on Ostium using Maxxit's Lazy Trading API. It provides programmatic endpoints to open and close positions, manage take profit / stop loss, fetch balances, positions, symbol lists, and LunarCrush market metrics. The skill is designed for automated workflows while enforcing required safety and parameter-resolution steps.

How this skill works

It calls Maxxit programmatic endpoints (club-details, symbols, lunarcrush, balance, positions, open-position, history, set-take-profit, set-stop-loss, close-position) in a prescribed sequence. Always fetch club-details first to obtain the user wallet and agent address, validate symbols via /symbols, fetch market data for pre-trade analysis, collect explicit trade parameters from the user, then execute trade endpoints. Responses contain required indices (tradeIndex, pairIndex, entryPrice, actualTradeIndex) that must be saved and used for later TP/SL or close operations.

When to use it

  • User wants to execute perpetual trades on Ostium
  • User needs account details, USDC/ETH balance, or portfolio positions
  • User wants market data or LunarCrush metrics for a symbol
  • User wants to open, close, or modify a position (TP/SL)
  • User wants position history or PnL data
  • User needs to validate available trading symbols before trading

Best practices

  • Always call /club-details first to get user_wallet and ostium_agent_address; never hardcode addresses
  • Resolve required parameters from prior API responses or explicit user input — never guess values
  • Validate markets with /symbols before trading and fetch LunarCrush/market data for context
  • Ask the user to confirm collateral, leverage, side, TP% and SL% and present sensible defaults
  • Save actualTradeIndex, tradeIndex, pairIndex, and entryPrice from responses; use them for subsequent TP/SL/close calls

Example use cases

  • Fetch the user’s Ostium USDC and ETH balances before allocating collateral
  • Retrieve symbols and LunarCrush metrics to identify high-sentiment opportunities
  • Open a new long/short position after presenting price, sentiment, and volatility to the user
  • List open positions and use returned tradeIndex/pairIndex to set take profit and stop loss
  • Fetch position history to compute realized/unrealized PnL for performance reporting

FAQ

Always call /club-details to get user_wallet and ostium_agent_address. Then validate the symbol via /symbols and fetch market data before asking the user for trade parameters.

Where do tradeIndex and pairIndex come from?

tradeIndex and pairIndex are returned by /open-position (actualTradeIndex) or by /positions. Call /positions if you need indexes for existing positions.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational