routing-dex-trades
Route trades across multiple DEXs to find optimal prices with minimal slippage and gas costs. Use when comparing DEX prices, finding optimal swap routes, analyzing price impact, splitting large orders, or assessing MEV risk. Trigger with phrases like "find best swap", "compare DEX prices", "route trade", "optimal swap route", "split order", "DEX aggregator", "check slippage", or "MEV protection".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill routing-dex-trades85
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
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that follows best practices. It provides specific capabilities, comprehensive trigger terms that users would naturally use, explicit 'Use when' guidance, and occupies a clearly defined niche in DeFi/DEX trading. The description is concise yet thorough, using third person voice appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Route trades across multiple DEXs', 'find optimal prices', 'minimal slippage', 'gas costs'. The description clearly articulates what the skill does with domain-specific but understandable terminology. | 3 / 3 |
Completeness | Clearly answers both 'what' (route trades, find optimal prices, minimize slippage/gas) AND 'when' with explicit 'Use when...' clause covering multiple scenarios plus a dedicated 'Trigger with phrases' section providing concrete examples. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'find best swap', 'compare DEX prices', 'route trade', 'optimal swap route', 'split order', 'DEX aggregator', 'check slippage', 'MEV protection'. These are realistic phrases a user working with DeFi would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused on DEX trading, swap routing, and DeFi-specific concerns like MEV risk and slippage. The specialized terminology (DEX, MEV, slippage) creates clear boundaries that would not conflict with general trading or finance skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent actionability and progressive disclosure. The concrete bash commands and example outputs make it immediately usable. However, it could be more concise by trimming the overview and prerequisites, and would benefit from explicit validation/confirmation steps before trade execution given the financial risk involved.
Suggestions
Add explicit validation checkpoints before trade execution (e.g., 'Verify quote freshness', 'Confirm amounts match expectations', 'Check wallet balance')
Trim the overview paragraph and prerequisites section - Claude understands DeFi concepts and the description already explains the purpose
Integrate MEV check into the main workflow rather than as a separate optional step, especially for larger trades
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanation (e.g., the overview paragraph restates what the description already covers, and the prerequisites section explains DeFi concepts Claude would know). The trade size recommendations table and output descriptions add value but could be more compact. | 2 / 3 |
Actionability | Provides fully executable bash commands with clear arguments and flags. Each step has concrete, copy-paste ready commands with specific examples of expected output (like the split recommendation showing exact numbers and percentages). | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced from configuration through various analysis modes, but lacks explicit validation checkpoints. For financial operations involving real trades, there should be verification steps before execution (e.g., 'verify quote is still valid', 'confirm amounts before proceeding'). The MEV check is good but positioned as optional rather than integrated into a safe execution workflow. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview, step-by-step instructions in the main file, and well-signaled one-level-deep references to examples.md and errors.md. External resources are appropriately linked at the end. Content is appropriately split between quick-start inline and detailed references. | 3 / 3 |
Total | 10 / 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 — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 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.