Bitget OpenAPI Skill

Operate Bitget public exchange market APIs through UXC with a curated OpenAPI schema, market-first discovery, and explicit private-auth boundary notes.

MIT-0 · Free to use, modify, and redistribute. No attribution required.
0 · 36 · 1 current installs · 1 all-time installs
MIT-0
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description claim public Bitget market reads and the files/instructions only reference public spot endpoints and the uxc helper; no unrelated credentials, hosts, or binaries are requested.
Instruction Scope
SKILL.md only instructs the agent to use uxc/bitget-openapi-cli to call specific public GET endpoints and to prefer narrow reads; it does not instruct reading local secrets, system files, or contacting unexpected endpoints. It explicitly states a private-auth boundary and read-only guardrails.
Install Mechanism
No install spec is present (instruction-only). The curated OpenAPI schema is included locally and references a raw.githubusercontent.com URL (a well-known host). No downloads from personal servers or archive extraction are required by the skill itself.
Credentials
The skill declares no required environment variables, no primary credential, and its documented operations are public-data-only. There is a clear note to avoid private-auth until a signer is provided.
Persistence & Privilege
always is false and model invocation is allowed (the platform default). The only operation that can modify local tooling is the recommended `uxc link ...` which registers a convenience CLI via the existing uxc tool; this is expected for a CLI-first skill but will create a local uxc link/alias if executed.
Assessment
This skill appears coherent and read-only, but before installing: (1) ensure you trust the uxc CLI — the skill relies on it and the `uxc link` command will register a local link/alias; (2) verify the curated OpenAPI schema source (references/bitget-v2.openapi.json) or inspect the local copy included in the skill rather than blindly fetching the raw.githubusercontent.com URL; (3) do not provide any private Bitget credentials to this skill (it is intentionally public-only); (4) be aware the agent may call api.bitget.com when invoked — if you want to prevent autonomous network calls, disable model invocation for this skill or avoid running the link/CLI commands. The included validate.sh is a harmless developer-time check that requires jq and ripgrep (rg) if you run it locally.

Like a lobster shell, security has layers — review code before you run it.

Current versionv1.0.0
Download zip
latestvk97e24dcej8f38cmwqramgxm49831j7z

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

SKILL.md

Bitget Exchange Skill

Use this skill to run Bitget public market-data operations through uxc + OpenAPI.

Reuse the uxc skill for shared execution, auth, and error-handling guidance.

Prerequisites

  • uxc is installed and available in PATH.
  • Network access to https://api.bitget.com.
  • Access to the curated OpenAPI schema URL:
    • https://raw.githubusercontent.com/holon-run/uxc/main/skills/bitget-openapi-skill/references/bitget-v2.openapi.json

Scope

This skill covers a curated Bitget public market surface for:

  • spot symbols and metadata
  • ticker reads
  • candlestick reads
  • order book snapshots

This skill does not cover:

  • private account endpoints in v1
  • private order placement or cancellation in v1
  • copy trading or P2P workflows

Authentication

Public market endpoints in this skill do not require credentials.

Bitget private APIs use provider-specific header signing and timestamp headers. Keep this v1 skill public-data-only until a reusable Bitget signer flow exists in uxc.

Core Workflow

  1. Use the fixed link command by default:

    • command -v bitget-openapi-cli
    • If missing, create it: uxc link bitget-openapi-cli https://api.bitget.com --schema-url https://raw.githubusercontent.com/holon-run/uxc/main/skills/bitget-openapi-skill/references/bitget-v2.openapi.json
    • bitget-openapi-cli -h
  2. Inspect operation help before execution:

    • bitget-openapi-cli get:/api/v2/spot/public/symbols -h
    • bitget-openapi-cli get:/api/v2/spot/market/tickers -h
  3. Prefer narrow spot reads first:

    • bitget-openapi-cli get:/api/v2/spot/market/tickers symbol=BTCUSDT
    • bitget-openapi-cli get:/api/v2/spot/market/orderbook symbol=BTCUSDT limit=20

Operations

  • get:/api/v2/spot/public/symbols
  • get:/api/v2/spot/market/tickers
  • get:/api/v2/spot/market/candles
  • get:/api/v2/spot/market/orderbook

Guardrails

  • Keep automation on the JSON output envelope; do not use --text.
  • Parse stable fields first: ok, kind, protocol, data, error.
  • Treat this v1 skill as read-only.
  • Keep symbol and candle ranges narrow unless the user explicitly wants a broader pull.
  • bitget-openapi-cli <operation> ... is equivalent to uxc https://api.bitget.com --schema-url <bitget_v2_openapi_schema> <operation> ....

References

Files

5 total
Select a file
Select a file to preview.

Comments

Loading comments…