htx-settlement
Settlement and insurance fund data for HTX USDT-M perpetuals — estimated next-settlement price, historical settlement records, and insurance fund balance/history. Public, no API key.
What this skill does
# HTX Settlement & Insurance Fund Reference data for HTX USDT-M perpetual **settlements** (the periodic mark-to-market events that net unrealized PnL into wallets) and the **insurance fund** (the contract platform's reserve for socialized loss prevention). ## When to use this skill Load this skill when the user asks about: - "When is the next settlement on BTC perpetual?" - "Estimated settlement price right now" - "Historical settlement records for ETH" - "How big is HTX's insurance fund?" - "Insurance fund balance trend" - "Has the insurance fund been paid out recently?" ## Underlying tool Drives `htx-cli`. Binary on `$PATH` or `$HTX_CLI_BIN`. Always pass `--json`. ## Endpoint catalog (4) | # | Method | Endpoint | CLI invocation | Description | |---|--------|----------|----------------|-------------| | 1 | GET | `/linear-swap-api/v1/swap_estimated_settlement_price` | `htx-cli futures call GET /linear-swap-api/v1/swap_estimated_settlement_price [--query contract_code=<code>] --json` | Estimated price for the next settlement | | 2 | GET | `/linear-swap-api/v1/swap_settlement_records` | `htx-cli futures call GET /linear-swap-api/v1/swap_settlement_records --query contract_code=<code>&start_time=<ms>&end_time=<ms> --json` | Historical settlement records (per-contract) | | 3 | GET | `/v1/insurance_fund_info` | `htx-cli futures call GET /v1/insurance_fund_info --json` | Current insurance fund balance per asset | | 4 | GET | `/v1/insurance_fund_history` | `htx-cli futures call GET /v1/insurance_fund_history --json` | Historical insurance fund balance time series | ## Concept reference | Term | Meaning | |------|---------| | **Settlement** | Periodic netting event where unrealized PnL becomes realized. HTX USDT-M settles **continuously** via mark price PnL — the "settlement records" endpoint refers to delivery-style settlements for any quarterly contracts. | | **Estimated settlement price** | Forward-looking price that would clear positions if settlement happened now. Useful for risk monitoring of margin levels. | | **Insurance fund** | Reserve pool funded by liquidation surplus. When a liquidated position can't be auctioned at the bankruptcy price, the fund covers the gap. Drawdowns indicate platform stress. | ## Contract code format USDT-M perpetual codes follow `<BASE>-USDT` (e.g. `BTC-USDT`). ## Typical queries → CLI | User question | CLI command | |---------------|-------------| | "BTC estimated settlement price" | `htx-cli futures call GET /linear-swap-api/v1/swap_estimated_settlement_price --query contract_code=BTC-USDT --json` | | "ETH settlement records last 30d" | `htx-cli futures call GET /linear-swap-api/v1/swap_settlement_records --query contract_code=ETH-USDT --json` | | "HTX insurance fund right now" | `htx-cli futures call GET /v1/insurance_fund_info --json` | | "Insurance fund last 90 days" | `htx-cli futures call GET /v1/insurance_fund_history --json` | ## Output guidance For insurance fund queries: - Show balance per asset (USDT main; ETH/BTC for COIN-M if relevant) - Show 30d / 90d change - Flag if fund has **decreased > 10%** in 7d (stress signal) For settlement queries: - Show next settlement time (UTC + local) - Show estimated price + delta from current mark - For historical records: aggregate by contract, count of settlements ## Related skills - `https://github.com/htx-exchange/htx-skills-hub/funding-rate` — settlements happen alongside funding events - `https://github.com/htx-exchange/htx-skills-hub/liquidation-stream` — liquidations feed the insurance fund - `https://github.com/htx-exchange/htx-skills-hub/derivatives-analyst` — *(planned Layer 2)* multi-signal pressure scoring
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.