odos

Odos smart order routing DEX aggregator. Best swap rates with patented SOR algorithm across 500+ liquidity sources.

Quality

48%

Does it follow best practices?

Impact

—

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/odos/SKILL.md

Quality

Discovery

32%

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 reads more like marketing copy than a functional skill description. It identifies the domain (Odos DEX aggregation) but lacks concrete actions the skill performs and entirely omits trigger guidance for when Claude should select it. The '500+ liquidity sources' and 'patented SOR algorithm' are promotional claims rather than actionable information for skill selection.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'token swap', 'best swap rate', 'DEX trade', 'exchange tokens', 'Odos', 'DeFi aggregator'.

Replace marketing language ('patented SOR algorithm', 'Best swap rates') with concrete actions like 'Fetches optimal swap routes across DEXs, builds swap transactions, compares token exchange rates'.

Include specific user scenarios such as 'Use when the user wants to swap ERC-20 tokens, find the best exchange rate, or route trades across multiple decentralized exchanges'.

Dimension	Reasoning	Score
Specificity	Names the domain (DEX aggregation, swap rates) and mentions the SOR algorithm and 500+ liquidity sources, but doesn't list specific concrete actions like 'execute token swaps', 'compare rates across DEXs', or 'build swap transactions'.	2 / 3
Completeness	Describes what it is (DEX aggregator with SOR algorithm) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'swap', 'DEX aggregator', and 'liquidity sources' that users might mention, but misses common variations like 'token swap', 'trade', 'exchange tokens', 'DeFi', 'best price', or specific chain names.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Odos' as a specific protocol and 'SOR algorithm' provides some distinctiveness, but 'DEX aggregator' and 'swap rates' could overlap with other DeFi/DEX-related skills without clearer scoping.	2 / 3
	Total	7 / 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 is a solid, actionable API skill with executable curl examples and clear endpoint documentation. Its main weaknesses are the lack of explicit validation/error-recovery steps in the workflow (especially important for financial transactions), and the monolithic structure that could benefit from splitting reference material into separate files. Some content like the feature list and referral fee explanation adds tokens without proportional value.

Suggestions

Add an explicit workflow section showing the full swap lifecycle: check allowance → approve if needed → get quote → validate quote response → assemble → verify transaction details → execute, with validation checkpoints at each step.

Move the supported chains table, multi-input/multi-output examples, and auxiliary endpoints (token list, liquidity sources, contract info) into separate reference files to improve progressive disclosure.

Remove or condense the emoji feature list and referral fee explanation sections — these don't provide actionable guidance and consume tokens.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with concrete examples, but includes some unnecessary content like the emoji-heavy feature list that Claude already knows, the referral fee explanation section, and the supported chains table which could be fetched via API. The multi-input and multi-output swap examples are somewhat redundant variations of the same API call.	2 / 3
Actionability	Provides fully executable curl commands with proper headers, JSON payloads, and jq parsing. The two-step workflow (quote → assemble) is copy-paste ready with clear variable substitution, and all API endpoints are concrete with real token addresses and chain IDs.	3 / 3
Workflow Clarity	The quote → assemble two-step flow is clear, and safety rules mention checking allowances and verifying outputs. However, there's no explicit validation checkpoint between steps (e.g., checking the quote response for errors before assembling), no feedback loop for error recovery, and the token approval step is mentioned in safety rules but never shown as an actual workflow step.	2 / 3
Progressive Disclosure	Content is reasonably organized with clear section headers, but it's a long monolithic file (~180 lines) with no bundle files to offload detail. The multi-input/multi-output examples, supported chains table, and auxiliary endpoints could be split into separate reference files. Links to external docs are provided but no internal progressive structure exists.	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: f45fcb5

Reviewed: 21 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.