LI.FI Skill

v2.0.1

v4 - Use LI.FI API for cross-chain and same-chain swaps, bridges, and contract calls. Use when quoting routes, validating chains/tokens, building transaction requests, and tracking status.

3· 2.7k·3 current·3 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the SKILL.md: the skill is an instruction-only wrapper for LI.FI API calls and only requests LIFI_API_KEY as expected.
Instruction Scope
Instructions are narrowly scoped to LI.FI endpoints and explicitly require using provided agent DeFi tools (defi_get_wallet, defi_approve_and_send, defi_send_transaction, etc.). Two notable operational choices to be aware of: a default slippage of 10% (0.10) and the directive to always add skipSimulation=true to /v1/quote requests — both affect transaction behavior and risk but are within the skill's stated domain.
Install Mechanism
No install spec or code files — instruction-only skill. Nothing is downloaded or written to disk by the skill itself.
Credentials
Only one environment variable (LIFI_API_KEY) is required and it directly corresponds to the LI.FI API usage described in the instructions.
Persistence & Privilege
always is false and the skill has no install that modifies system or other skills. It does rely on other agent tools to access user wallets and send transactions, which is expected for a DeFi integration.
Assessment
This skill is internally consistent with its purpose, but review these before installing: 1) It requires your LI.FI API key — ensure you trust the agent and that the key has appropriate (minimal) permissions and can be revoked. 2) The skill expects to call other agent DeFi tools (defi_get_wallet, defi_approve_and_send, defi_send_transaction, etc.) — confirm the agent will prompt you before broadcasting or approving on-chain transactions. 3) Default slippage is high (10%) and skipSimulation=true is enforced; both can increase risk of unexpected outcomes — consider setting lower slippage or confirming each trade. 4) Test with small amounts first and verify quoted transactions on LI.FI docs (https://docs.li.fi/). Revoke the API key if you stop using the skill.

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

latestvk97740htkxh3vavn7195mj3dd980rmx1

License

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

Runtime requirements

🔁 Clawdis
EnvLIFI_API_KEY
Primary envLIFI_API_KEY

Comments