paraswap

ParaSwap DEX aggregator. Best swap rates across 300+ liquidity sources on Ethereum, Polygon, BSC, Arbitrum, and more.

Quality

48%

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/paraswap/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 reads like a marketing tagline rather than a functional skill description. It identifies the domain (DEX aggregation) and mentions supported chains, but lacks concrete actions the skill can perform and entirely omits 'Use when...' guidance, making it difficult for Claude to reliably select this skill at the right time.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user wants to swap tokens, find best exchange rates, trade on DEXes, or mentions ParaSwap.'

List specific concrete actions the skill performs, e.g., 'Fetches optimal swap routes, builds swap transactions, compares rates across DEXes, estimates gas costs.'

Include additional natural trigger terms users might say, such as 'token swap', 'trade tokens', 'exchange crypto', 'best price', 'DeFi swap', or 'liquidity'.

Dimension	Reasoning	Score
Specificity	Names the domain (DEX aggregation, swap rates) and mentions specific details like '300+ liquidity sources' and supported chains, but doesn't list concrete actions like 'execute swaps', 'compare rates', 'build transactions', etc.	2 / 3
Completeness	Describes what it is (DEX aggregator for best swap rates) 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, so this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'swap', 'DEX', 'ParaSwap', and chain names (Ethereum, Polygon, BSC, Arbitrum), but misses common user terms like 'token swap', 'exchange tokens', 'trade', 'DeFi', 'slippage', or 'best price'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'ParaSwap' specifically and 'DEX aggregator' provides some distinctiveness, but without explicit triggers it could overlap with other DeFi or swap-related skills. The description reads more like a tagline than a skill selector.	2 / 3
	Total	7 / 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.

The skill provides strong actionable content with executable curl commands covering the full ParaSwap API surface. However, it lacks an explicit end-to-end workflow with validation checkpoints (e.g., check allowance → approve → get quote → verify price impact → build tx → confirm with user → execute), and the partner fee promotion and marketing language consume tokens without adding instructional value. The content would benefit from tighter organization and explicit multi-step sequencing.

Suggestions

Add an explicit numbered workflow that sequences the full swap process: check allowance → approve if needed → get price quote → validate price impact → build transaction → confirm with user → execute, with validation checkpoints at each step.

Remove or significantly condense the partner fee section and marketing language (emoji-heavy feature list, 'Leading DEX aggregator') to save tokens—Claude doesn't need to be sold on the product.

Add a feedback loop for error recovery: e.g., if PRICE_TIMEOUT occurs, automatically re-fetch the quote; if price impact exceeds threshold, warn and await confirmation before proceeding.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with concrete API examples, but includes unnecessary marketing language ('Leading DEX aggregator'), emoji decoration, and the partner fee section is verbose and promotional. The supported chains table and feature bullet list add moderate value but could be tighter.	2 / 3
Actionability	Provides fully executable curl commands for all key operations (get price, build transaction, check allowance, get approval, limit orders, token list). Commands include proper variable setup, query parameters, and jq formatting for output parsing—all copy-paste ready.	3 / 3
Workflow Clarity	The implicit workflow (get price → build transaction → execute) is present but not explicitly sequenced as a numbered workflow. Safety rules mention checking allowance before swap, but there's no explicit validation checkpoint or feedback loop between getting a quote and building the transaction (e.g., verifying price impact before proceeding).	2 / 3
Progressive Disclosure	Content is reasonably organized with clear section headers, but everything is in a single monolithic file. The limit orders section, supported chains table, and error handling could be split into referenced files. External links to docs are provided but no bundle files support progressive disclosure.	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.