sushiswap-api

REST API for optimized token swapping (including executable transaction generation), swap quoting, and pricing using the SushiSwap Aggregator. Use this skill when the user wants to: - Get a swap quote between two tokens on 40+ evm networks - Generate executable swap transaction data - Fetch token prices for a specific network or token - Retrieve token metadata - Discover supported AMM liquidity sources - Integrate SushiSwap swapping or pricing logic via HTTP/REST (and not the SushiSwap Javascript API)

1.38x

Quality

78%

Does it follow best practices?

Impact

90%

1.38x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/0xmasayoshi/sushiswap-api/SKILL.md

Quality

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 a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes natural trigger terms users would use, explicitly answers both what and when, and carves out a distinct niche by specifying SushiSwap REST API and distinguishing it from the JavaScript API alternative.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: swap quoting, executable transaction generation, pricing, token metadata retrieval, discovering supported AMM liquidity sources. These are clearly defined capabilities.	3 / 3
Completeness	Clearly answers both 'what' (REST API for token swapping, quoting, pricing via SushiSwap Aggregator) and 'when' with an explicit 'Use this skill when the user wants to:' clause listing six specific trigger scenarios.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'swap quote', 'token prices', 'SushiSwap', 'evm networks', 'REST', 'HTTP', 'AMM', 'liquidity sources', 'swap transaction'. Also explicitly distinguishes from the JavaScript API, which helps with disambiguation.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: SushiSwap Aggregator REST API specifically. The explicit exclusion of the JavaScript API further reduces conflict risk with related skills. The domain (DeFi token swapping via SushiSwap REST) is very specific.	3 / 3
	Total	12 / 12 Passed

Implementation

57%

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

The skill is well-structured with good progressive disclosure, delegating detailed API specs to an OpenAPI schema file. However, it lacks concrete executable examples (e.g., curl commands or code snippets for common operations like getting a quote), and the referrer parameter section is repetitive. The workflow would benefit from explicit validation checkpoints and example request/response pairs.

Suggestions

Add at least one concrete curl or code example for the most common operation (e.g., getting a swap quote) to make the skill immediately actionable without needing to parse the OpenAPI schema first.

Consolidate the four bullet points about the `referrer` parameter into a single clear constraint statement to reduce redundancy.

Add a validation/verification step in the workflow, such as 'Check response status and validate response shape against schema before using swap data' — especially important since this involves financial transactions.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but includes some unnecessary explanation (e.g., 'It aggregates liquidity from multiple DEXs to determine the best execution route' and the fee customization section is somewhat verbose for what Claude needs). The referrer parameter section repeats the same constraint four different ways.	2 / 3
Actionability	The skill delegates almost all concrete details to the OpenAPI schema file rather than providing executable examples. There are no curl commands, no example request/response pairs, and no copy-paste ready code. The workflow is procedural but abstract ('Load the schema, discover endpoints, construct requests').	2 / 3
Workflow Clarity	Steps are listed in a reasonable sequence (load schema → discover endpoints → construct requests → validate parameters), but there are no validation checkpoints or feedback loops. For an API integration skill involving financial transactions, missing error recovery workflows and no explicit 'verify response before proceeding' step is a gap.	2 / 3
Progressive Disclosure	Clear overview structure with well-signaled one-level-deep references to the OpenAPI schema and OPENAPI.md guidance file. Content is appropriately split between the skill overview and reference materials.	3 / 3
	Total	9 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: Demerzels-lab/elsamultiskillagent
Commit: 45f9fac

Reviewed: 2 months 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.