Navigate OneKey App Swap, Bridge, Limit, and Stock/Market flows. Use for token selection, quotes, review/build/send, providers, cold start, and history/status; use the Perps skill for Hyperliquid.
71
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Medium
Suggest reviewing before use
Use this skill as a map to the owning code and contract. Let current code, payloads, and runtime behavior decide implementation details.
entry -> selection -> quote -> review -> execution -> history/status.| Task | Start here | Read next |
|---|---|---|
| Swap selection, quote, review, or send | Swap state/actions, view hooks, background service | Architecture, Code map |
| Wallet, Send, Earn, Buy, or Market handoff | Source params, then settled Swap state | Architecture |
| Bridge, Limit, Stock, privacy, or provider work | Capability, payload, and lifecycle adapter | Provider contracts |
| Cold start, default asset, tab, or first-frame issue | Route seed, persisted display state, readiness | Architecture |
| Pending, history, status, restart, or repair | Persistent owner and status source | Provider contracts |
| Receive-only filtering | Receive and AssetSelector before any Swap handoff | Code map |
State the entry, first wrong owner, and identities that matter. Run nearby tests and the repository-required checks, then prove the affected route and payload on the owning platform. Report any runtime or provider evidence you could not get.
Related skills: $1k-perps-module, $1k-tradingview-communication,
$1k-state-management, $1k-cross-platform, $1k-defi-module-integration.
863e41c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.