lifi

LI.FI cross-chain bridge and DEX aggregator. Swap tokens across 30+ blockchains with best rates and routes.

Quality

52%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/0xterrybit/lifi/SKILL.md

Quality

Discovery

40%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a clear niche (LI.FI cross-chain bridging) with good distinctiveness, but suffers from missing explicit trigger guidance and incomplete action coverage. The lack of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill over others.

Suggestions

Add a 'Use when...' clause with trigger terms like 'bridge tokens', 'cross-chain swap', 'transfer between chains', 'best swap rate', or 'multi-chain exchange'

Expand specific actions beyond 'swap tokens' to include 'compare bridge routes', 'estimate gas fees', 'find best rates across DEXs'

Include common user phrases like 'move ETH to Polygon', 'swap on multiple chains', or 'find cheapest bridge'

Dimension	Reasoning	Score
Specificity	Names the domain (cross-chain bridge, DEX aggregator) and mentions 'swap tokens' as an action, but lacks comprehensive specific actions like 'compare routes', 'estimate fees', or 'execute transactions'.	2 / 3
Completeness	Describes what it does (swap tokens, bridge, aggregate DEX) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant terms like 'swap tokens', 'blockchains', 'bridge', and 'DEX' that users might say, but misses common variations like 'crypto swap', 'token exchange', 'cross-chain transfer', or specific chain names.	2 / 3
Distinctiveness Conflict Risk	The combination of 'LI.FI', 'cross-chain bridge', 'DEX aggregator', and '30+ blockchains' creates a clear niche that is unlikely to conflict with other skills - it's specifically about multi-chain crypto swapping.	3 / 3
	Total	8 / 12 Passed

Implementation

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides excellent actionable curl examples for LI.FI API interactions with concrete token addresses and chain IDs. However, it lacks a clear end-to-end workflow with validation steps, particularly around the critical transaction execution phase which is left vague. The content could be more concise by removing redundant integrator fee declarations and moving reference tables to separate files.

Suggestions

Add a complete end-to-end workflow section with numbered steps: 1) Get quote, 2) Check approval status, 3) Approve if needed, 4) Execute transaction, 5) Poll status until DONE/FAILED

Complete the 'Execute Transaction' section with concrete code showing how to sign and submit the transaction using a specific tool (e.g., cast, ethers.js)

Move the integrator fee configuration to a single location and reference it from examples instead of repeating the values

Add validation checkpoints like 'Verify quote.estimate.toAmount meets minimum expected output before proceeding'

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some redundant information like the extensive bridge/chain tables that could be fetched dynamically, and the integrator fee configuration is repeated multiple times across examples.	2 / 3
Actionability	Provides fully executable curl commands with concrete examples, specific token addresses, chain IDs, and jq parsing. Commands are copy-paste ready with clear variable substitution patterns.	3 / 3
Workflow Clarity	Individual operations are clear, but the end-to-end workflow (quote → approve → execute → check status) lacks explicit sequencing and validation checkpoints. The 'Execute Transaction' section is notably incomplete, just saying 'requires a signing mechanism' without concrete guidance.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections and tables, but everything is in one file. The extensive reference tables (chains, bridges, errors) could be split into separate reference files, and external links are provided but not integrated as progressive disclosure.	2 / 3
	Total	9 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	9 / 11 Passed

Repository: Demerzels-lab/elsamultiskillagent
Commit: 45f9fac

Reviewed: 27 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.