0x-swap
0x Protocol DEX aggregator. Swap tokens at the best rates across 9+ liquidity sources on Ethereum, Polygon, BSC, and more.
52
59%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xterrybit/0x-swap/SKILL.mdQuality
Discovery
54%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 effectively identifies its niche as a 0x Protocol DEX aggregator with good trigger terms and distinctiveness. However, it lacks an explicit 'Use when...' clause, which is critical for Claude to know when to select this skill. The specificity could also be improved by listing more concrete actions beyond just swapping.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to swap tokens, find best exchange rates, compare DEX prices, or trade crypto across chains.'
List additional concrete actions such as 'fetch swap quotes, compare prices across DEXes, handle token approvals, estimate gas costs' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (DEX aggregation, token swapping) and mentions specific actions (swap tokens, best rates), but doesn't list multiple concrete actions beyond swapping. It mentions chains and liquidity sources but lacks detail on other capabilities like limit orders, quote fetching, or approval handling. | 2 / 3 |
Completeness | Describes what it does (swap tokens via 0x Protocol DEX aggregator) but has no explicit 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent (not even implied beyond the domain), this scores at 1. | 1 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: '0x Protocol', 'DEX aggregator', 'swap tokens', 'best rates', 'liquidity sources', 'Ethereum', 'Polygon', 'BSC'. These cover common terms a user would use when wanting to perform token swaps. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific references to '0x Protocol', 'DEX aggregator', specific blockchain networks, and liquidity sources. This is unlikely to conflict with other skills due to its clear niche in DeFi token swapping. | 3 / 3 |
Total | 9 / 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 functional API reference skill with strong actionability—concrete curl commands, real token addresses, and proper API parameters. Its main weaknesses are redundant fee configuration repeated across multiple sections, missing validation/verification steps in the swap workflow, and a monolithic structure that could benefit from splitting reference tables into separate files. The hardcoded swap fee recipient address baked into every example is also a notable design choice.
Suggestions
Add explicit validation steps to the Execute Swap workflow: verify token allowance with a concrete command, check quote freshness, and include an error recovery loop for failed transactions.
Consolidate the swap fee configuration into a single section instead of repeating it in the env vars table, fee breakdown section, and every curl example—use variable references instead.
Split reference tables (common token addresses, supported chains, error codes) into a separate REFERENCE.md file and link to it from the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some redundancy—the swap fee configuration is repeated in the environment variables table, the fee breakdown section, and again in every single curl command. The supported chains table partially duplicates the API base URLs table. The common token addresses and chain IDs are useful reference material, but the fee promotion text is unnecessarily verbose. | 2 / 3 |
Actionability | The skill provides fully executable curl commands with proper headers, query parameters, and jq formatting. Token addresses, chain IDs, and API endpoints are all concrete and copy-paste ready. The Execute Swap section is slightly incomplete (step 3 defers to wallet integration), but this is a reasonable boundary. | 3 / 3 |
Workflow Clarity | The Execute Swap section has a clear 3-step sequence, and Safety Rules provide good guardrails. However, there are no explicit validation checkpoints between steps—no verification that the quote is still valid before execution, no check that token allowance is sufficient (just a rule saying to check it without showing how), and no error recovery feedback loop for failed transactions. | 2 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear sections and tables, but it's a long monolithic file with no bundle files to offload reference material. The common token addresses, supported chains, and detailed API examples could be split into separate reference files. Links to external docs are provided but no internal file references exist. | 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 | |
- Repository
- Demerzels-lab/elsamultiskillagent
- Commit
f45fcb5
- 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.