okx/agent-skills

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

author: okx   version: "1.5.0"   homepage: "https://www.okx.com"

version: "1.5.0"   homepage: "https://www.okx.com"   agent:

homepage: "https://www.okx.com"

[Credential-related source omitted]

**Claude Code / Hermes / Generic (`claude-code.default.json`):** - scheduler.type = `"cron"` — scheduled via **OS crontab → `scripts/scan.sh`** (zero LLM token cost), notification via TG / Lark curl from the script itself.

- scheduler.type = `"cron"` — scheduled via **OS crontab → `scripts/scan.sh`** (zero LLM token cost), notification via TG / Lark curl from the script itself.

[Credential-related source omitted]

TG and Lark are **standalone push channels** — they work regardless of whether the agent client is open. On OS-crontab platforms, scheduled scans send notifications via direct curl. On **OpenClaw**, the scheduled scan runs in an isolated cr

[Credential-related source omitted]

- Neither set → TG not available 2. Check `platform.notify.lark_webhook` or Lark MCP tools:    - Webhook set and valid (starts with `https://` and contains `/hook/`) → Lark ready

2. Check `platform.notify.lark_webhook` or Lark MCP tools:    - Webhook set and valid (starts with `https://` and contains `/hook/`) → Lark ready    - Webhook set but format invalid (does not start with `https://` or missing `/hook/`) → war

- Webhook set and valid (starts with `https://` and contains `/hook/`) → Lark ready

- Webhook set but format invalid (does not start with `https://` or missing `/hook/`) → warn: "Lark webhook 格式无效，跳过 Lark" → continue to next channel

- If user picks Telegram → guide setting `TELEGRAM_BOT_TOKEN` and `TELEGRAM_CHAT_ID` env vars - If user picks Lark → ask for webhook URL, validate format (starts with `https://`, contains `/hook/`), write to `platform.notify.lark_webhook`

- If user picks Lark → ask for webhook URL, validate format (starts with `https://`, contains `/hook/`), write to `platform.notify.lark_webhook`

6. Not received → troubleshoot (see `notify-channels.md`) 7. 5 min no response → ping once 8. Session channel → skip confirmation

8. Session channel → skip confirmation

These use **OS scheduler → `scripts/scan.sh`**. The script does everything (CLI calls, filter, dedup, render, curl notifications) with **zero LLM cost**.

cat > ~/Library/LaunchAgents/com.okx.earn-hunter.plist << PLIST <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0">

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

- LaunchAgent plist paths must be absolute (no `~`). The activation flow expands `$HOME` at generation time. - `RunAtLoad: true` means the first scan runs immediately after loading. - The script reads `config.json` / `platform.json`, writes

- `RunAtLoad: true` means the first scan runs immediately after loading. - The script reads `config.json` / `platform.json`, writes `state.json` / `notify.log`, and sends notifications via curl to TG Bot API or Lark Webhook itself. No agent

- The script reads `config.json` / `platform.json`, writes `state.json` / `notify.log`, and sends notifications via curl to TG Bot API or Lark Webhook itself. No agent involvement needed at tick time.

[Credential-related source omitted]

`launchctl unload ~/Library/LaunchAgents/com.okx.earn-hunter.plist && rm -f ~/Library/LaunchAgents/com.okx.earn-hunter.plist`

Scheduled scans run via OS crontab (no LLM session). **Always use direct curl to TG Bot API or Lark Webhook** for notifications. `scripts/scan.sh` does the curl itself.

On OpenClaw the scheduled scan runs as an **isolated cron agent turn** created via the in-session `cron` tool. Delivery is via the cron job's **`announce`** mode, which pushes the turn's output back to the conversation channel that created 

|------|---------|---------|---------| | Interactive session | Any | Markdown in conversation | Full (can reply) | | OS crontab (scheduled) | Claude Code / Hermes / Generic | curl TG/Lark | Push only |

| Interactive session | Any | Markdown in conversation | Full (can reply) | | OS crontab (scheduled) | Claude Code / Hermes / Generic | curl TG/Lark | Push only | | In-session cron (scheduled) | OpenClaw | cron `announce` → conversation cha

| OS crontab (scheduled) | Claude Code / Hermes / Generic | curl TG/Lark | Push only |

| Direct webhook | N/A | curl TG Bot API / Lark Webhook | Push only |

[Credential-related source omitted]

[Credential-related source omitted]

- Neither set → not available 2. **Lark webhook**    - `platform.json` `.notify.lark_webhook` is non-empty, starts with `https://`, and contains `/hook/` → Lark ready

2. **Lark webhook**    - `platform.json` `.notify.lark_webhook` is non-empty, starts with `https://`, and contains `/hook/` → Lark ready    - Value present but format invalid → **incomplete**: warn "Lark webhook 格式无效（需以 https:// 开头且包含 /hook

- `platform.json` `.notify.lark_webhook` is non-empty, starts with `https://`, and contains `/hook/` → Lark ready

curl -s "https://api.telegram.org/bot${TOKEN}/sendMessage" \

[Credential-related source omitted]

curl -s -X POST "<webhook_url>" \

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

# Step 1: 验证 bot token 有效性 curl -s "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/getMe"

[Credential-related source omitted]

[Credential-related source omitted]

# Step 2: 验证 chat_id 有效性 curl -s "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/getChat?chat_id=${TELEGRAM_CHAT_ID}"

[Credential-related source omitted]

[Credential-related source omitted]

# Step 3: 重发测试消息 curl -s "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendMessage" \

[Credential-related source omitted]

[Credential-related source omitted]

1. 检查 webhook URL 格式（必须以 `https://` 开头，包含 `/hook/`）

[Credential-related source omitted]

- **`openclaw-cron`** (OpenClaw) — scheduled via the in-session **`cron` agent tool**, isolated + light-context, delivered back to the conversation via `announce`. See [OpenClaw](#openclaw-in-session-cron-tool). - **`cron`** (Claude Code / 

- **`cron`** (Claude Code / Hermes / Generic) — scheduled via **OS crontab + `okx` CLI + curl notifications**. No LLM sessions spawned — zero token cost. See [OS Crontab](#os-crontab-configuration).

The script (pure shell + jq) calls the `okx` CLI directly, filters/dedups, and sends notifications via curl to TG/Lark — with **zero LLM cost**. It exits silently (no output, nothing sent) when there are no new opportunities and `verboseLog

#!/usr/bin/env bash

badge_inprogress) [[ "$LANG_SEL" == en ]] && echo "in-progress" || echo "进行中" ;;     badge_upcoming)   [[ "$LANG_SEL" == en ]] && echo "upcoming" || echo "预告" ;;     flash_cta)        [[ "$LANG_SEL" == en ]] && echo "→ Subscribe now ( https

badge_upcoming)   [[ "$LANG_SEL" == en ]] && echo "upcoming" || echo "预告" ;;     flash_cta)        [[ "$LANG_SEL" == en ]] && echo "→ Subscribe now ( https://okx.com/ul/rhNe3q )" || echo "→ 立即申购（ https://okx.com/ul/rhNe3q ）" ;;     fixed_fi

flash_cta)        [[ "$LANG_SEL" == en ]] && echo "→ Subscribe now ( https://okx.com/ul/rhNe3q )" || echo "→ 立即申购（ https://okx.com/ul/rhNe3q ）" ;;

rm -f "$_ef"; printf '%s' "$out"; return 0

if is_auth_error "$out $_stderr"; then rm -f "$_ef"; printf '%s' "$out $_stderr"; return 1; fi

rm -f "$_ef"

local tg_ready=0 lark_ready=0   [[ -n "$tg_token" && -n "$tg_chat" ]] && tg_ready=1   if [[ "$lark" == https://* && "$lark" == *"/hook/"* ]]; then lark_ready=1; fi

[Credential-related source omitted]

if [[ "$lark" == https://* && "$lark" == *"/hook/"* ]]; then lark_ready=1; fi

local resp   resp=$(curl -s "https://api.telegram.org/bot${TOKEN}/sendMessage" \

resp=$(curl -s "https://api.telegram.org/bot${TOKEN}/sendMessage" \

local resp   resp=$(curl -s -X POST "$webhook" -H "Content-Type: application/json" -d "$payload" 2>/dev/null)

resp=$(curl -s -X POST "$webhook" -H "Content-Type: application/json" -d "$payload" 2>/dev/null)

→ 立即申购（ https://okx.com/ul/rhNe3q ）

author: okx   version: "1.5.0"   homepage: "https://www.okx.com"

version: "1.5.0"   homepage: "https://www.okx.com"   agent:

homepage: "https://www.okx.com"

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

[Credential-related source omitted]

author: okx   version: "1.5.0"   homepage: "https://www.okx.com"

version: "1.5.0"   homepage: "https://www.okx.com"   agent:

homepage: "https://www.okx.com"

[Credential-related source omitted]

author: okx   version: "1.5.0"   homepage: "https://www.okx.com"

version: "1.5.0"   homepage: "https://www.okx.com"   agent:

homepage: "https://www.okx.com"

[Credential-related source omitted]

- **Security:** Never ask users to paste API keys or secrets into chat. - **Output:** Always pass `--json` to list/query commands and render results as a Markdown table — never paste raw terminal output. - **Network errors:** If commands fa

- **Output:** Always pass `--json` to list/query commands and render results as a Markdown table — never paste raw terminal output. - **Network errors:** If commands fail with a connection error, prompt user to check VPN: `curl -I https://w

- **Network errors:** If commands fail with a connection error, prompt user to check VPN: `curl -I https://www.okx.com`

1. Run parallel pre-display fetch (spot price + balance + products) as above

author: okx   version: "1.5.0"   homepage: "https://www.okx.com"

version: "1.5.0"   homepage: "https://www.okx.com"   agent:

homepage: "https://www.okx.com"

author: okx   version: "1.5.0"   homepage: "https://www.okx.com"

version: "1.5.0"   homepage: "https://www.okx.com"   agent:

homepage: "https://www.okx.com"

[Credential-related source omitted]

author: okx   version: "1.5.0"   homepage: "https://www.okx.com"

version: "1.5.0"   homepage: "https://www.okx.com"   agent:

homepage: "https://www.okx.com"

author: okx   version: "1.5.0"   homepage: "https://www.okx.com"

version: "1.5.0"   homepage: "https://www.okx.com"   agent:

homepage: "https://www.okx.com"

[Credential-related source omitted]

- **Security:** Never ask users to paste API keys or secrets into chat. - **Output:** Always pass `--json` to list/query commands and render results as a Markdown table — never paste raw terminal output. - **Network errors:** If commands fa

- **Output:** Always pass `--json` to list/query commands and render results as a Markdown table — never paste raw terminal output. - **Network errors:** If commands fail with a connection error, prompt user to check VPN: `curl -I https://w

- **Network errors:** If commands fail with a connection error, prompt user to check VPN: `curl -I https://www.okx.com`

author: okx   version: "1.5.0"   homepage: "https://www.okx.com"

version: "1.5.0"   homepage: "https://www.okx.com"   agent:

homepage: "https://www.okx.com"

[Credential-related source omitted]

- Batch operations (batch cancel, batch amend) are available via MCP tools directly if needed - Position mode (`net` vs `long_short_mode`) affects whether `--posSide` is required - **Network errors**: If commands fail with a connection erro

- Position mode (`net` vs `long_short_mode`) affects whether `--posSide` is required - **Network errors**: If commands fail with a connection error, prompt user to check VPN: `curl -I https://www.okx.com` - **Capability discovery**: Run `ok

- **Network errors**: If commands fail with a connection error, prompt user to check VPN: `curl -I https://www.okx.com`

author: okx   version: "1.5.0"   homepage: "https://www.okx.com"

version: "1.5.0"   homepage: "https://www.okx.com"   agent:

homepage: "https://www.okx.com"