kyberswap

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

Quality

52%

Does it follow best practices?

Impact

—

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

40%

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 a clear niche (KyberSwap DEX aggregation) and is distinctive, but it reads more like a marketing tagline than a functional skill description. It lacks specific actionable capabilities (e.g., swap tokens, compare rates) and entirely omits trigger guidance for when Claude should select this skill.

Suggestions

Add a 'Use when...' clause with natural trigger terms like 'swap tokens', 'trade crypto', 'find best DEX rate', 'token exchange', or 'DeFi swap'.

Replace the marketing-style phrasing with concrete actions: e.g., 'Swaps tokens, compares rates across DEXs, finds optimal trade routes, and executes trades on 17+ EVM chains via KyberSwap aggregator.'

Include common user-facing keywords like 'swap', 'token', 'DeFi', 'liquidity', and specific chain names (Ethereum, Polygon, etc.) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (DEX aggregation) and mentions some capabilities (best rates, dynamic trade routing, multi-chain/multi-DEX), but doesn't list specific concrete actions like 'swap tokens', 'compare rates', 'execute trades', or 'find optimal routes'.	2 / 3
Completeness	Describes what it is (DEX aggregator with routing across DEXs/chains) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also only partially described, warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant terms like 'DEX aggregator', 'trade routing', and 'chains', but misses common user terms like 'swap', 'token swap', 'exchange tokens', 'trade crypto', 'DeFi', or specific chain names that users would naturally mention.	2 / 3
Distinctiveness Conflict Risk	KyberSwap is a specific named product/protocol, and the combination of 'DEX aggregator', '100+ DEXs', '17+ chains', and 'dynamic trade routing' creates a very distinct niche that is unlikely to conflict with other skills.	3 / 3
	Total	8 / 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 skill provides strong actionable API examples with executable curl commands for KyberSwap's aggregator, which is its primary strength. However, it lacks integrated validation steps in the swap workflow (e.g., checking approval, verifying route before building tx, handling failed builds), and includes some marketing-style content that wastes tokens. The safety rules are listed abstractly rather than woven into the workflow as concrete checkpoints.

Suggestions

Integrate safety rules as explicit validation checkpoints within the swap workflow (e.g., after getting route: 'Check if priceImpact > 1%, if so WARN user and require confirmation before proceeding to build')

Add a token approval check step between getting the route and building the transaction, since ERC-20 swaps require allowance verification

Remove the marketing-style features bullet list and the repeated description—Claude doesn't need to be sold on the product

Add error handling/validation after each API call (e.g., check for .data.routeSummary existence before passing to build step)

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with concrete API examples, but includes some unnecessary padding like the features bullet list (Claude doesn't need marketing copy about '100+ DEXs'), the links section, and the repeated description in the header. The supported chains table is borderline—useful reference but lengthy.	2 / 3
Actionability	Provides fully executable curl commands with proper variable setup, query parameters, and jq formatting for all key operations (get route, build transaction, get tokens, limit orders). Commands are copy-paste ready with clear variable substitution points.	3 / 3
Workflow Clarity	The two-step swap workflow (get route → build transaction) is present but lacks explicit validation checkpoints. There's no feedback loop for checking if the route response is valid before building the transaction, no verification of approval status, and the safety rules are listed as abstract principles rather than integrated into the workflow steps.	2 / 3
Progressive Disclosure	Content is reasonably organized with clear sections, but everything is in a single monolithic file. The supported chains table, limit orders, and error handling could be split into referenced files. Links to external docs are provided but no bundle files exist to offload detailed content.	2 / 3
	Total	9 / 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: f45fcb5

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