Prompt
Specify a webhook-driven task for OpenClaw
Describe event inputs, validation, deduplication, and intended actions before integration work.
OpenClawDevelopment & Engineering
Dave AI
using-hyperliquid-adapter
How to use Hyperliquid adapter data (meta, funding, candles, orderbooks) and execution surfaces (orders/transfers) in Wayfinder Paths, including required executor wiring.
instructions.md
--- name: using-hyperliquid-adapter-8b174d7b122e description: How to use Hyperliquid adapter data (meta, funding, candles, orderbooks) and execution surfaces (orders/transfers) in Wayfinder Paths, including required executor wiring. metadata: tags: wayfinder, hyperliquid, perps, spot, funding, candles, execution --- ## When to use Use this skill when you are: - Pulling Hyperliquid market data (perp + spot) - Using time series (funding history, OHLCV candles) - Planning order execution (market/limit/stop), transfers, or withdrawals ## How to use - [rules/high-value-reads.md](rules/high-value-reads.md) - Data sources + I/O shapes for market data and time series - [rules/deposits-withdrawals.md](rules/deposits-withdrawals.md) - Bridge2 deposit/withdraw mechanics (chain, minimums, timing, monitoring) - [rules/execution-opportunities.md](rules/execution-opportunities.md) - Order/transfer/withdraw flows and required executor injection - [rules/outcomes.md](rules/outcomes.md) - HIP-4 outcome markets (binary/multi-outcome prediction contracts, asset id encoding; dispatched inline by `place_market_order` / `place_limit_order` when `asset_name` starts with `#`) - [rules/gotchas.md](rules/gotchas.md) - Asset IDs, spot naming, and common integration pitfalls--- name: using-hyperliquid-adapter-8b174d7b122e description: How to use Hyperliquid adapter data (meta, funding, candles, orderbooks) and execution surfaces (orders/transfers) in Wayfinder Paths, including required executor wiring. metadata: tags: wayfinder, hyperliquid, perps, spot, funding, candles, execution --- ## When to use Use this skill when you are: - Pulling Hyperliquid market data (perp + spot) - Using time series (funding history, OHLCV candles) - Planning order execution (market/limit/stop), transfers, or withdrawals ## How to use - [rules/high-value-reads.md](rules/high-value-reads.md) - Data sources + I/O shapes for market data and time series - [rules/deposits-withdrawals.md](rules/deposits-withdrawals.md) - Bridge2 deposit/withdraw mechanics (chain, minimums, timing, monitoring) - [rules/execution-opportunities.md](rules/execution-opportunities.md) - Order/transfer/withdraw flows and required executor injection - [rules/outcomes.md](rules/outcomes.md) - HIP-4 outcome markets (binary/multi-outcome prediction contracts, asset id encoding; dispatched inline by `place_market_order` / `place_limit_order` when `asset_name` starts with `#`) - [rules/gotchas.md](rules/gotchas.md) - Asset IDs, spot naming, and common integration pitfalls
Platform guidance
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.