LI.FI Skill

**Judgement:** A strong, production-oriented LI.FI integration that is well-aligned with OpenClaw DeFi tools and suitable as the default path for cross-chain and same-chain swaps/bridges. It is feature-complete for typical routing use cases and carefully restricts agents to LI.FI’s API and system DeFi tools. **Key strengths:** - Enforces a single, correct LI.FI base URL and mandatory API key header, reducing configuration errors. - Integrates tightly with defi_get_wallet, defi_send_transaction, defi_approve_and_send, and defi_send_sui_transaction, including correct handling of ERC-20 approvals and Sui-specific execution. - Covers core endpoints: chains, tokens, quotes (with tx data), advanced routes, contractCalls, tools listing, and status tracking. - Requires use of LI.FI’s transactionRequest and gasLimit, avoiding brittle hand-crafted calldata. **Main risks / limitations:** - Default slippage of **10%** is high; if an agent/user does not override it, trades on illiquid pairs or volatile markets may clear at materially worse prices than expected. - Safety controls around user intent (e.g., explicit confirmation for large or cross-chain transfers) are not described; responsibility is pushed to the calling agent/UX. - Reliance on a single external API (LI.FI) and an environment-provided `LIFI_API_KEY`; failure or misconfiguration there will break functionality with no described fallback. - Contract calls via `/v1/quote/contractCalls` are explicitly marked BETA; agents should treat them as more experimental and be conservative with size and complexity. **Recommended scenarios:** - Default routing layer for any agent that needs **cross-chain or same-chain DeFi swaps and bridging**, especially when correctness and tool integration are more important than raw customizability. - Wallets or portfolio managers that want to support **Sui and EVM** flows via a single integrations surface and don’t want to maintain DEX-level integrations themselves. - Automation or strategy agents that need to **quote multiple routes, inspect fees and outputs, then auto-execute** via standardized OpenClaw DeFi tools. For high-value transactions or sensitive strategies, adopters should: (1) reduce slippage below 10% unless absolutely necessary, and (2) layer additional user confirmations and balance checks on top of this skill.