lifi
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.
[](https://agentverus.ai/skill/8e421f49-f1f2-43e4-8768-721df9214a55)Community Comments
Public comments are the active feedback surface on skill reports right now. Use them to share implementation notes, edge cases, and operator context.
Sign in to comment on this skill
No comments yet. Be the first to share your thoughts.
Keep this report moving through the activation path: rescan from the submit flow, capture real-world interactions, and wire the trust endpoint into your automation.
https://agentverus.ai/api/v1/skill/8e421f49-f1f2-43e4-8768-721df9214a55/trustUse your saved key to act on this report immediately instead of returning to onboarding.
Use these current-skill command blocks to keep this exact report moving through your workflow.
curl -X POST https://agentverus.ai/api/v1/interactions \
-H "Authorization: Bearer at_your_api_key" \
-H "Content-Type: application/json" \
-d '{"agentPlatform":"openclaw","skillId":"8e421f49-f1f2-43e4-8768-721df9214a55","interactedAt":"2026-03-15T12:00:00Z","outcome":"success"}'curl https://agentverus.ai/api/v1/skill/8e421f49-f1f2-43e4-8768-721df9214a55/trustCategory Scores
Findings (7)
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
Found comprehensive secret collection pattern: "List tokens"
→ Skills should not instruct collection of all tokens, keys, or credentials. Access only the specific credentials needed and declare them.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
Found financial/payment actions pattern: "wallet"
→ Financial actions should always require explicit user confirmation and should be clearly documented.
The skill includes a URL whose query parameters look like they carry cookies, auth state, or token material. URLs are commonly logged and replayed, so credential-bearing parameters expand the dependency risk surface even on first-party domains. Related auth/profile context: - overlapping signals from the same local context — Unknown external reference
→ Avoid query-string credential transport. Prefer secure headers, dedicated cookie APIs, or other mechanisms that do not expose bearer material in URLs.
The skill references a raw content hosting service which is classified as medium risk.
→ Use official package registries instead of raw content URLs. Raw URLs can be changed without notice.
The skill does not include explicit safety boundaries defining what it should NOT do.
→ Add a 'Safety Boundaries' section listing what the skill must NOT do (e.g., no file deletion, no network access beyond needed APIs).