lifi
Build LI.FI Cross-Chain API Integrations
Cross-chain swap and DeFi integrations require many chain, token, status, and approval details. This skill gives Claude, Codex, and Claude Code concise LI.FI API guidance for quotes, routes, vaults, and intents.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "lifi" from https://skillstore.io/skills/internet-court-lifi.md and its manifest at https://skillstore.io/api/skills/internet-court-lifi/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "lifi". Bridge USDC from Arbitrum to Base with LI.FI.
Expected outcome:
- Use a Core API quote with source and destination chain IDs.
- Check the approval address and wait for any approval transaction.
- Re-fetch the quote before signing if the first quote is stale.
- Poll status until the transfer reaches a terminal state.
Using "lifi". Find depositable USDC vaults on Base.
Expected outcome:
- Query Earn vaults with chain, asset, and Composer support filters.
- Compare APY, TVL, caps, KYC, and withdrawal settings.
- Use the selected vault address as the Composer destination token.
Using "lifi". Handle a partial bridge completion.
Expected outcome:
- Confirm the received token and destination chain from status data.
- Explain that value may be received in a different token.
- Offer a same-chain recovery swap when gas costs are reasonable.
Security Audit
High RiskOf 147 static findings, 133 are false positives caused by Markdown formatting, placeholders, API terms, or non-executing endpoint references. Fourteen findings confirm intended outbound calls to LI.FI services, while two semantic findings identify high-risk transaction and vault-selection workflows. No prompt injection attempt was found.
Confirmed security concerns (2)
Capability review items (14)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
π Network access (31)
βοΈ External commands (50)
π Env variables (3)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/internet-court-lifi/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/internet-court-lifi?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/internet-court-lifi?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/internet-court-lifi/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/internet-court-lifi.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA Β· BibTeX Β· CFF)
APA citation
internet-court. (2026). lifi security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/internet-court-lifi/audits/2BibTeX citation
@techreport{internet-court-internet-court-lifi-2026,
author = {internet-court},
title = {lifi security audit report (audit version 2)},
institution = {Skillstore},
year = {2026},
number = {2},
url = {https://skillstore.io/skills/internet-court-lifi/audits/2},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "lifi security audit report (audit version 2)"
version: "unspecified"
type: report
authors:
- name: "internet-court"
date-released: "2026-07-19"
url: "https://skillstore.io/skills/internet-court-lifi/audits/2"
identifiers:
- type: other
value: "skillstore:internet-court-lifi:audit:2"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Build swap and bridge flows
Plan LI.FI quote, approval, signing, and status steps for cross-chain token movement.
Evaluate DeFi vault integrations
Use Earn and Composer guidance to discover vaults and design deposit or withdrawal flows.
Design agent transaction workflows
Create guarded API workflows for route selection, intent orders, polling, and recovery handling.
Try These Prompts
Explain the LI.FI quote flow for bridging USDC from Arbitrum to Optimism. Include approval checks and status polling.
Draft parameters for a same-chain swap from ETH to USDC on Polygon. Include slippage, route order, and stale quote handling.
Design an Earn discovery flow for Base USDC vaults. Include filters, data freshness, and Composer deposit steps.
Review my backend plan for LI.FI Intents. Flag signing, expiry, refund, and status tracking gaps.
Best Practices
- Re-fetch quotes after approvals and before any signing step.
- Use exact approvals and the quoted approval address for ERC-20 tokens.
- Cache discovery endpoints and back off when rate limits are returned.
Avoid
- Hardcoding spender addresses instead of using the quoted approval address.
- Assuming a timeout means failure before checking status and explorer links.
- Selecting vaults from APY alone without checking caps, locks, and KYC.
Frequently Asked Questions
Does this skill execute token swaps?
Do I need a LI.FI API key?
Can it help with DeFi deposits?
Does it cover non-EVM chains?
How should failed routes be handled?
Is this financial advice?
Developer Details
Author
internet-courtLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
3f6e026a3363e0954ede7bef0cfe88d4475de137
Maintenance freshness
7/18/2026
Usage
1 downloads Β· 0 views
File structure