Apex Trading & Analysis

Trade and monitor ApeX perpetual futures. Check balances, view positions with P&L, place/cancel orders, execute market trades, or submit trade reward enrollments. Use when the user asks about ApeX trading, portfolio status, crypto positions, activity enrollments, or wants to execute trades on ApeX.

Security Scan

The skill appears to implement an ApeX trading client (matching its description) but the package/registry metadata omits the fact it requires multiple sensitive credentials — including an Omni seed phrase — and uses an alpha SDK dependency; those inconsistencies warrant caution before installing or providing secrets.

Purpose & Capability

The code and SKILL.md clearly implement ApeX trading, portfolio, and market-analysis features which justify the listed dependencies (apexomni SDK, ethers-related libs, node-fetch). However the registry metadata claims no required environment variables or primary credential, while both SKILL.md and every private-operation script require APEX_API_KEY, APEX_API_SECRET, APEX_API_PASSPHRASE and APEX_OMNI_SEED. That mismatch (metadata says none; runtime needs multiple secrets including a seed phrase) is incoherent and concerning.

Instruction Scope

Runtime instructions are explicit: npm install then run the provided node scripts. SKILL.md and scripts limit external network calls to ApeX endpoints and CoinGecko (both expected). The instructions do not instruct the agent to read unrelated system files, but they do show examples of passing full credentials in the environment when invoking commands. SKILL.md also includes trigger phrases and defaults (reward id 300001) which are acceptable but should be noted.

Install Mechanism

There is no formal install spec in the registry (instruction-only), but the code contains a package.json and requires running `npm install` in the scripts folder. Dependencies come from npm (package-lock entries look standard) — no arbitrary download URLs were used. The apexomni-connector-node dependency is pinned to an '0.3.2-alpha.1' release (an alpha release), which raises moderate risk because it may be unreviewed/unstable; otherwise the install mechanism is standard npm usage.

Credentials

Private operations require multiple sensitive environment variables: APEX_API_KEY, APEX_API_SECRET, APEX_API_PASSPHRASE and APEX_OMNI_SEED (seed phrase/private key). Such secrets are proportionate for a trading client, but the registry metadata does not declare them — meaning an agent/platform might not surface the required secrets to the user up-front. The presence of a seed phrase (APEX_OMNI_SEED) is high-privilege and should be handled with extreme care (never provide it to remote/cloud agents unless you trust execution environment).

Persistence & Privilege

The skill is not always-enabled and is user-invocable (normal). It writes a local trading-state.json file inside the skill directory (scripts/check-positions.mjs) but does not request system-wide config changes or modify other skills. Autonomous invocation is allowed by default on the platform (disable-model-invocation=false), which is typical; combine that with providing live credentials only if you trust the agent environment.

What to consider before installing

This skill is functionally consistent with an ApeX trading client, but there are two red flags you should address before installing or giving it secrets: (1) the registry metadata incorrectly lists no required environment variables while the SKILL.md and all scripts require APEX_API_KEY, APEX_API_SECRET, APEX_API_PASSPHRASE and APEX_OMNI_SEED (a seed phrase/private key), and (2) the SDK dependency is an 'alpha' npm release. Practical recommendations: do not provide your live Omni seed to a remote or cloud-hosted agent; prefer testnet or read-only credentials for initial testing; confirm the origin of apexomni-connector-node on npm (and audit that package); run npm install and the scripts in an isolated sandbox (or container) first; restrict API key permissions where possible (avoid withdrawal or full admin rights); and ask the skill author or publisher for a canonical source/homepage and an explanation for why the registry metadata omitted the required env vars. If you are not comfortable auditing the code and dependencies yourself, avoid supplying the seed or use only a testnet account.

ApeX Trading Skill

Full trading and portfolio management for ApeX perpetual futures exchange.

Prerequisites

Install dependencies once:

cd skills/apex/scripts && npm install

Authentication

Private operations require API credentials and an Omni seed:

• APEX_API_KEY
• APEX_API_SECRET
• APEX_API_PASSPHRASE
• APEX_OMNI_SEED

Important: APEX_OMNI_SEED is required by the SDK for order-related operations. Treat it like a private key/seed phrase and keep it strictly local. Do not share it or commit it.

Testnet:

• Set APEX_TESTNET=1 (or APEX_ENV=qa).

Core Operations

Market Data (Public)

Get price for a coin:

node scripts/apex.mjs price BTC

List available symbols:

node scripts/apex.mjs meta

Portfolio Monitoring (Private)

Check balance:

APEX_API_KEY=... APEX_API_SECRET=... APEX_API_PASSPHRASE=... APEX_OMNI_SEED=... \
  node scripts/apex.mjs balance

View positions with P&L:

APEX_API_KEY=... APEX_API_SECRET=... APEX_API_PASSPHRASE=... APEX_OMNI_SEED=... \
  node scripts/apex.mjs positions

Check open orders:

APEX_API_KEY=... APEX_API_SECRET=... APEX_API_PASSPHRASE=... APEX_OMNI_SEED=... \
  node scripts/apex.mjs orders

View trade history:

APEX_API_KEY=... APEX_API_SECRET=... APEX_API_PASSPHRASE=... APEX_OMNI_SEED=... \
  node scripts/apex.mjs fills

Trading Operations

All trading commands require the ApeX API credentials and seed.

Place limit orders:

APEX_API_KEY=... APEX_API_SECRET=... APEX_API_PASSPHRASE=... APEX_OMNI_SEED=... \
  node scripts/apex.mjs limit-buy BTC 0.1 45000

APEX_API_KEY=... APEX_API_SECRET=... APEX_API_PASSPHRASE=... APEX_OMNI_SEED=... \
  node scripts/apex.mjs limit-sell ETH 1 3000

Market orders:

APEX_API_KEY=... APEX_API_SECRET=... APEX_API_PASSPHRASE=... APEX_OMNI_SEED=... \
  node scripts/apex.mjs market-buy BTC 0.5

APEX_API_KEY=... APEX_API_SECRET=... APEX_API_PASSPHRASE=... APEX_OMNI_SEED=... \
  node scripts/apex.mjs market-sell ETH 2

Cancel orders:

APEX_API_KEY=... APEX_API_SECRET=... APEX_API_PASSPHRASE=... APEX_OMNI_SEED=... \
  node scripts/apex.mjs cancel-all

APEX_API_KEY=... APEX_API_SECRET=... APEX_API_PASSPHRASE=... APEX_OMNI_SEED=... \
  node scripts/apex.mjs cancel-all BTC

Submit trade reward enrollment:

APEX_API_KEY=... APEX_API_SECRET=... APEX_API_PASSPHRASE=... APEX_OMNI_SEED=... \
  node scripts/apex.mjs submit-reward 12345

Output Formatting

All commands output JSON. Parse and format for chat display:

For balance/portfolio:

• Show total equity and available balance
• List positions with size, entry price, unrealized P&L
• Summarize open orders

For trade execution:

• Confirm order details before executing
• Report order ID and status after execution
• Show filled price if immediately executed

Safety Guidelines

Before executing trades:

1. Confirm trade parameters with user (symbol, size, side, price)
2. Show current price and position for context
3. Calculate estimated cost/proceeds

Position sizing:

• Warn if trade is >20% of account equity
• Suggest appropriate sizes based on account balance

Price checks:

• For limit orders, compare limit price to current market price
• Warn if limit price is >5% away from market (likely mistake)

Error Handling

Common errors:

• "Missing APEX credentials" → Set API key, secret, passphrase, and seed
• "Unknown symbol" → Check available symbols with meta
• HTTP errors → Check network connection and API status

When errors occur:

• Show the error message to user
• Suggest fixes (set env vars, check symbol names, verify balance)
• Don't retry trades automatically

Trigger Phrases

Use submit-reward when the user expresses enrollment intent for OpenClaw activities or contests. If no reward ID is provided, default to 300001.

English examples:

• "Enroll me in the OpenClaw trading contest"
• "Register for OpenClaw activity"
• "Sign up for the OpenClaw contest"
• "Join the OpenClaw trading contest"

Chinese examples:

• "报名活动"
• "参加活动"
• "报名OpenClaw活动"
• "参加OpenClaw交易赛"

If the user provides a reward ID, use it. Otherwise use the default.

Workflow Examples

"How's my ApeX portfolio?"

1. Run balance to get total equity
2. Run positions to get open positions
3. Format summary: equity, positions with P&L, total unrealized P&L

"Buy 0.5 BTC on ApeX"

1. Run price BTC to get current price
2. Confirm with user: "Buy 0.5 BTC at market? Current price: $X. Estimated cost: $Y"
3. Execute market-buy BTC 0.5
4. Report result

"What's the current BTC price on ApeX?"

1. Run price BTC
2. Format response: "BTC: $X on ApeX"

"Close my ETH position"

1. Run positions to get current ETH position size
2. If long → market-sell, if short → market-buy
3. Execute with position size
4. Report result

"Enroll me in OpenClaw Trading Contest"

1. Run submit-reward (defaults to 300001)
2. Report result

Advanced Features

List all available symbols:

node scripts/apex.mjs meta

Notes

• Symbols use -USDT format for trading (e.g., BTC-USDT).
• Public market data endpoints often use BTCUSDT format.
• Prices are in USD.
• ApeX uses perpetual futures, not spot trading.
• Check references/api.md for API details.