0x-swap
0x Protocol DEX aggregator. Swap tokens at the best rates across 9+ liquidity sources on Ethereum, Polygon, BSC, and more.
Install with Tessl CLI
npx tessl i github:Demerzels-lab/elsamultiskillagent --skill 0x-swap60
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 core functionality (DEX aggregation for token swaps) and mentions specific blockchains, providing moderate specificity. However, it lacks explicit trigger guidance ('Use when...') which significantly impacts completeness, and could benefit from more natural user-facing keywords like 'trade', 'exchange', or 'convert'.
Suggestions
Add a 'Use when...' clause with trigger terms like 'swap tokens', 'trade crypto', 'exchange tokens', 'best swap rate', 'DEX trade'
Include common user phrases and variations: 'trade', 'exchange', 'convert', 'crypto swap', 'token exchange', 'DeFi swap'
List more specific actions: 'get swap quotes', 'compare rates across DEXs', 'execute token swaps', 'find best liquidity'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (DEX aggregator, token swapping) and mentions specific actions (swap tokens, best rates), but doesn't list comprehensive concrete actions like 'get quotes', 'compare prices', 'execute trades', etc. | 2 / 3 |
Completeness | Describes what it does (swap tokens via 0x aggregator) 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 keywords (swap, tokens, DEX, Ethereum, Polygon, BSC) but misses common variations users might say like 'exchange', 'trade', 'convert crypto', 'token exchange', or specific chain names like 'Binance Smart Chain'. | 2 / 3 |
Distinctiveness Conflict Risk | The '0x Protocol' branding and specific chains provide some distinctiveness, but 'swap tokens' and 'DEX aggregator' could overlap with other crypto/DeFi skills without clearer differentiation. | 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 skill provides solid, actionable API integration guidance with executable curl examples and comprehensive reference tables. However, it lacks validation checkpoints in the swap execution workflow (critical for financial operations), includes some unnecessary decorative elements, and could benefit from splitting reference data into separate files.
Suggestions
Add explicit validation steps in the Execute Swap workflow: verify quote price impact, check token allowances, and confirm transaction success before proceeding
Remove emoji decorations and the feature bullet list - these add tokens without actionable value
Move token address and chain ID reference tables to separate files (e.g., TOKENS.md, CHAINS.md) and link from main skill
Complete step 3 of Execute Swap with actual executable code or explicit guidance on what wallet integration is needed
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is reasonably efficient with good use of tables and code examples, but includes some unnecessary elements like emoji decorations, feature bullet lists that describe rather than instruct, and the 'Links' section which adds little value for Claude. | 2 / 3 |
Actionability | Provides fully executable curl commands with proper headers, parameters, and jq parsing. Code examples are copy-paste ready with clear variable substitution patterns and complete API calls. | 3 / 3 |
Workflow Clarity | The 'Execute Swap' section shows a 3-step process but lacks validation checkpoints - no verification that the quote is acceptable before signing, no error handling between steps, and step 3 is incomplete with just a comment about wallet integration. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but everything is in one file. Reference tables (token addresses, chain IDs) could be split to separate files, and the document is somewhat long at ~180 lines without external references. | 2 / 3 |
Total | 9 / 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.