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".
78
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/crypto/dex-aggregator-router/skills/routing-dex-trades/SKILL.mdQuality
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 clearly defines a specific DeFi trade routing capability with concrete actions, explicit trigger guidance, and natural user-facing keywords. It follows the recommended structure with 'Use when...' and 'Trigger with...' clauses, and its domain-specific focus makes it highly distinguishable from other skills. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: routing trades across DEXs, finding optimal prices, minimizing slippage and gas costs, comparing DEX prices, analyzing price impact, splitting large orders, and assessing MEV risk. | 3 / 3 |
Completeness | Clearly answers both 'what' (route trades across DEXs for optimal prices with minimal slippage/gas) and 'when' (explicit 'Use when...' clause with multiple trigger scenarios, plus a dedicated 'Trigger with phrases like...' section). | 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 terms DeFi users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused on DEX trade routing, slippage, MEV risk, and swap optimization. The domain-specific terminology (DEX, MEV, slippage, swap routes) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a well-structured overview of DEX trade routing with clear CLI commands and good organization. However, it suffers from redundancy between Instructions and Examples sections, lacks inline output examples, and references bundle files that don't exist. For a financial operation with real risk (MEV, slippage), the absence of validation checkpoints and confirmation steps is a notable gap.
Suggestions
Add inline sample output for at least one command (e.g., the quick quote) so Claude knows what to expect and can validate results.
Add explicit validation/confirmation steps in the workflow, e.g., 'Verify the quote is within expected range before proceeding' or 'Confirm split allocation percentages sum to 100%'.
Remove or consolidate the Examples section—it duplicates commands from Instructions without adding new information. Use that space for actual output examples instead.
Provide the referenced bundle files (implementation.md, errors.md, examples.md) or remove references to them to avoid broken navigation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some redundancy—the Examples section largely repeats commands already shown in Instructions. The Output section descriptions and Overview are reasonably tight but could be trimmed. | 2 / 3 |
Actionability | Provides concrete CLI commands which is good, but all commands reference scripts that aren't provided in the bundle. There's no actual executable code—just CLI invocations of a script we can't verify exists. No sample output is shown inline, and implementation details are deferred to references that don't exist in the bundle. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced from simple quote to full analysis, and the error handling table is useful. However, there are no validation checkpoints—no step says 'verify the quote before proceeding' or 'confirm the split allocation looks reasonable before execution.' For operations involving real financial trades with MEV risk, the absence of explicit verification/confirmation steps is a gap. | 2 / 3 |
Progressive Disclosure | References to implementation.md, errors.md, and examples.md are well-signaled and one level deep, which is good structure. However, no bundle files are provided, so we can't verify these references exist. The Examples section duplicates Instructions content rather than adding value, suggesting the content split could be better organized. | 2 / 3 |
Total | 8 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.