kyberswap

KyberSwap DEX aggregator. Best rates across 100+ DEXs on 17+ chains with dynamic trade routing.

Quality

60%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/0xterrybit/kyberswap/SKILL.md

Quality

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 product and its core value proposition (aggregating DEX rates) but reads more like marketing copy than skill selection guidance. It lacks explicit trigger conditions, concrete user actions, and natural language terms users would actually say when needing this skill.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to swap tokens, find best crypto exchange rates, or trade on decentralized exchanges'

Include natural user terms: 'swap', 'token exchange', 'crypto swap', 'best price for tokens', 'DeFi trading'

List concrete actions the skill performs: 'Find optimal swap routes, compare rates across DEXs, execute token swaps, check liquidity'

Dimension	Reasoning	Score
Specificity	Names the domain (DEX aggregator) and mentions key features (best rates, dynamic trade routing), but doesn't list concrete user actions like 'swap tokens', 'compare rates', or 'execute trades'.	2 / 3
Completeness	Describes what it is (DEX aggregator with routing) 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 'DEX', 'aggregator', 'trade routing' which are relevant but technical. Missing natural user terms like 'swap', 'token exchange', 'crypto trading', 'best price', or chain names users might mention.	2 / 3
Distinctiveness Conflict Risk	'KyberSwap' is a specific product name which helps, but 'DEX aggregator' could overlap with other DeFi/trading skills. The description doesn't clearly carve out its unique niche versus other swap or trading tools.	2 / 3
	Total	7 / 12 Passed

Implementation

87%

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-crafted skill with excellent actionability and conciseness. The executable curl examples with real addresses and clear parameter documentation make it immediately usable. The main weakness is the lack of explicit validation steps between getting a route and building/executing the transaction, which is important for financial operations.

Suggestions

Add explicit validation checkpoint between route retrieval and transaction building (e.g., verify amountOut meets minimum expectations, check price impact percentage)

Include a feedback loop for handling route errors before proceeding to build transaction (e.g., 'If route returns INSUFFICIENT_LIQUIDITY, reduce amount and retry')

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient, providing only necessary information without explaining basic concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context.	3 / 3
Actionability	Provides fully executable curl commands with all parameters, concrete examples with real token addresses, and copy-paste ready code. The variable placeholders are clearly marked and the jq filters show expected output structure.	3 / 3
Workflow Clarity	The two-step workflow (get route → build transaction) is present but lacks explicit validation checkpoints. No verification step to confirm the route is valid before building, and no feedback loop for error recovery between steps.	2 / 3
Progressive Disclosure	Well-organized with clear sections progressing from basic (get route) to advanced (limit orders). External documentation links are provided for deeper reference. Content is appropriately structured for a skill of this scope.	3 / 3
	Total	11 / 12 Passed

Validation

81%

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 — 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: 45f9fac

Reviewed: 27 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.