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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured, highly actionable, and uses progressive disclosure effectively with verified reference files. It loses points on conciseness (duplication between Examples and Instructions) and workflow clarity (no explicit validation checkpoints).

Suggestions

Remove or trim the Examples section, since its commands duplicate the Instructions section verbatim; instead link to examples.md for distinct worked scenarios.

Add a brief verification step (e.g., confirming a quote is non-stale or re-running --mev-check before executing a large order) so the workflow includes an explicit checkpoint.

Consolidate the Resources list so reference-file purposes are stated once rather than repeated from the in-section "See …" pointers.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven with no concept padding, but the Examples section repeats commands verbatim from Instructions and the Resources section restates purposes of reference files already linked inline.	2 / 3
Actionability	Every instruction is a fully executable command with concrete arguments (e.g. "python ${CLAUDE_SKILL_DIR}/scripts/dex_router.py ETH USDC 5.0 --compare") backed by a real script, making it copy-paste ready.	3 / 3
Workflow Clarity	Six numbered usage scenarios give a clear sequence and an Error Handling table aids recovery, but there are no explicit validation checkpoints or validate→fix→retry steps within the workflow.	2 / 3
Progressive Disclosure	A concise overview SKILL.md points to one-level-deep, clearly signaled references (implementation.md, errors.md, examples.md) that all exist as real files, with a TOC for navigation.	3 / 3
	Total	10 / 12 Passed

Description

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.

The description is strong across all dimensions: it states concrete capabilities, gives an explicit "Use when" trigger, and lists natural trigger phrases in a dedicated clause. Third-person voice is used throughout, so no voice penalty applies.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Route trades across multiple DEXs", "find optimal prices", "splitting large orders", "assessing MEV risk" — matching the anchor for several specific concrete actions.	3 / 3
Completeness	Explicitly answers "what" (route trades across DEXs for optimal prices) and "when" via a clear "Use when comparing DEX prices…" clause, so both halves are present and explicit.	3 / 3
Trigger Term Quality	A dedicated "Trigger with phrases like" list supplies natural user phrasings ("find best swap", "compare DEX prices", "split order", "check slippage") with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	A clear DEX-aggregation niche with distinct triggers ("DEX aggregator", "MEV protection", "optimal swap route") makes overlap with unrelated skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 607d11b

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.