odos
Odos smart order routing DEX aggregator. Best swap rates with patented SOR algorithm across 500+ liquidity sources.
Install with Tessl CLI
npx tessl i github:Demerzels-lab/elsamultiskillagent --skill odos71
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 identifies the domain (DEX aggregation) and highlights a key differentiator (patented SOR algorithm), but reads more like marketing copy than actionable skill guidance. It lacks concrete actions Claude can perform and critically omits any 'Use when...' trigger guidance, making it difficult for Claude to know when to select this skill from a large skill library.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'swap tokens', 'find best DEX rate', 'trade on Odos', 'compare liquidity sources', or 'DeFi exchange'.
Replace marketing language ('Best swap rates', 'patented') with concrete actions like 'Execute token swaps, compare rates across DEXs, route orders for optimal pricing'.
Include common user phrases and variations: 'crypto swap', 'token exchange', 'DeFi trading', 'cross-chain swap' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (DEX aggregator, swap rates, liquidity sources) and mentions the SOR algorithm, but doesn't list concrete actions like 'execute swaps', 'compare rates', or 'route 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. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'swap', 'DEX', 'aggregator', and 'liquidity sources', but misses common user phrases like 'token exchange', 'trade crypto', 'best price', or 'DeFi swap'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'Odos' brand name and 'SOR algorithm' provide some distinctiveness, but 'DEX aggregator' and 'swap rates' could overlap with other crypto/DeFi trading skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with excellent actionability through complete, executable curl examples and efficient token usage. The main weakness is workflow clarity - while the quote→assemble pattern is shown, there's no explicit validation loop for checking allowances, verifying quotes, or handling errors before transaction execution. The safety rules section exists but isn't integrated into a step-by-step workflow.
Suggestions
Integrate safety rules into a numbered workflow: 1. Get quote → 2. Verify price impact < 1% → 3. Check/set allowance → 4. Assemble → 5. Display details for user confirmation → 6. Execute
Add an allowance check/approval example before the swap flow, as ERC20 approvals are required for non-native token swaps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, presenting API endpoints with executable examples without explaining what DEX aggregators are or how blockchain works. Every section serves a purpose with no padding. | 3 / 3 |
Actionability | Provides fully executable curl commands with proper variable substitution, jq parsing, and complete request bodies. Examples are copy-paste ready with clear parameter documentation. | 3 / 3 |
Workflow Clarity | The two-step quote→assemble flow is shown but lacks explicit validation checkpoints. Safety rules are listed but not integrated into the workflow sequence. Missing verification steps between quote and execution. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from basic swaps to advanced multi-input/output scenarios. External links to docs are provided for deeper reference. Content is appropriately scoped for a SKILL.md. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%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 | |
- Reviewed
Table of Contents
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.