← 返回 Skills 市场
joshlin111

Apex Trading & Analysis

作者 joshlin111 · GitHub ↗ · v1.0.3
cross-platform ⚠ suspicious
2930
总下载
7
收藏
5
当前安装
4
版本数
在 OpenClaw 中安装
/install apex-trading
功能描述
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.
使用说明 (SKILL.md)

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.
安全使用建议
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.
功能分析
Type: OpenClaw Skill Name: apex-trading Version: 1.0.3 The OpenClaw AgentSkills skill bundle 'apex-trading' is designed for legitimate cryptocurrency trading on the ApeX perpetual futures exchange. All code and documentation (SKILL.md, README.md) consistently align with this stated purpose, providing functionalities for market analysis, portfolio monitoring, and trade execution. Sensitive API credentials (keys, secrets, Omni seed) are explicitly required for private operations, and the documentation includes strong warnings about their security and proper handling (e.g., 'Treat it like a private key/seed phrase and keep it strictly local. Do not share it or commit it.' in SKILL.md and README.md). The scripts communicate with the official ApeX API and CoinGecko for market data, with no evidence of data exfiltration to unauthorized endpoints or malicious execution patterns. The instructions for the AI agent in SKILL.md and README.md include responsible safety guidelines for trading (e.g., 'Confirm trade parameters with user', 'Warn if trade is >20% of account equity'), indicating a focus on secure and controlled operation rather than prompt injection for harmful objectives. Local file I/O (`trading-state.json`) is for legitimate state management. No obfuscation or suspicious dependencies were found.
能力评估
⚠ 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.
如何使用
  1. 确保已安装 OpenClaw（本地或 Docker 部署）
  2. 在对话框中输入安装命令：/install apex-trading
  3. 安装完成后，直接呼叫该 Skill 的名称或使用 /apex-trading 触发
  4. 根据 Skill 的参数说明提供必要输入，即可获得结构化输出
版本历史
v1.0.3
- Added trigger phrase guidance for "submit-reward", including defaulting to reward ID 300001 if none is provided. - Now lists English and Chinese example trigger phrases for OpenClaw enrollment. - No changes to core functionality or trading commands. - Added .DS_Store in scripts directory (no functional impact).
v1.0.2
- Added support for submitting trade reward enrollments via the new `submit-reward` command. - Expanded skill usage to include handling activity enrollments (such as trading contests) in addition to trading and portfolio monitoring. - Updated security guidance for `APEX_OMNI_SEED`, emphasizing it must remain private and local. - Provided an example workflow for enrolling in trading contests. - Updated description and documentation to reflect the new features.
v1.0.1
- Clarified the importance of keeping the `APEX_OMNI_SEED` private and strictly local in authentication instructions. - Added instructions for submitting trade reward enrollment via the `submit-reward` command. - No changes to core trading or portfolio management functionality. - Updated documentation for improved clarity and security practices.
v1.0.0
Initial release of the ApeX Trading skill. - Enables trading and portfolio management for ApeX perpetual futures, including viewing balances, positions, P&L, and order management. - Supports market data queries, active order tracking, and viewing trade history. - Allows execution and cancellation of market and limit orders, with safety checks on trade sizing and price distance. - Requires setting API credentials and Omni seed for private or trading operations. - All outputs are in JSON and guidelines are provided for parsing and displaying key data, confirmations, and error handling. - Includes usage examples and advice for preventing execution mistakes.
元数据
Slug apex-trading
版本 1.0.3
许可证 —
累计安装 5
当前安装数 5
历史版本数 4
常见问题

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. 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件，目前累计下载 2930 次。

如何安装 Apex Trading & Analysis？

在 OpenClaw 或 Claude Code 对话框中运行命令「/install apex-trading」即可一键安装，无需额外配置。

Apex Trading & Analysis 是免费的吗？

是的，Apex Trading & Analysis 完全免费（开源免费），可自由下载、安装和使用。

Apex Trading & Analysis 支持哪些平台？

Apex Trading & Analysis 跨平台运行，可在任意部署了 OpenClaw / Claude Code 的环境中使用（cross-platform）。

谁开发了 Apex Trading & Analysis？

由 joshlin111（@joshlin111）开发并维护，当前版本 v1.0.3。

推荐 Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463283 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259410 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200423 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191115 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190156 · by oswalpalash

💬 留言讨论