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)
84
78%
Does it follow best practices?
Impact
90%
1.38xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xmasayoshi/sushiswap-api/SKILL.mdQuality
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 strong skill description that clearly articulates specific capabilities (swap quoting, transaction generation, pricing, metadata retrieval), provides explicit trigger guidance via a 'Use this skill when...' clause with multiple scenarios, and distinguishes itself from a related JavaScript API skill. The description is well-structured, uses third person voice, and includes natural keywords that users would employ when seeking this functionality.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: swap quoting, executable transaction generation, pricing, token metadata retrieval, discovering supported AMM liquidity sources, and integration via HTTP/REST. | 3 / 3 |
Completeness | Clearly answers both 'what' (REST API for token swapping, quoting, pricing via SushiSwap Aggregator) and 'when' (explicit 'Use this skill when the user wants to...' clause with six specific trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'swap quote', 'token prices', 'swap transaction', 'SushiSwap', 'EVM networks', 'REST', 'HTTP', 'AMM', 'liquidity sources', 'token metadata'. Also explicitly distinguishes from the JavaScript API, which helps with disambiguation. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: SushiSwap Aggregator REST API specifically, on 40+ EVM networks, and explicitly excludes the JavaScript API variant. Unlikely to conflict with other skills. | 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-organized with good progressive disclosure, delegating detailed API specs to reference files. However, it lacks concrete executable examples (e.g., a sample curl request for a swap quote) and repeats certain constraints redundantly. The workflow would benefit from validation checkpoints and at least one end-to-end example showing a complete request/response cycle.
Suggestions
Add at least one concrete, copy-paste ready example (e.g., a curl command for a swap quote with sample parameters and expected response shape) to improve actionability.
Consolidate the four bullet points about the `referrer` parameter into one or two concise statements to reduce redundancy.
Add a validation/verification step in the workflow, such as checking the quote response before proceeding to swap execution, to improve workflow clarity.
| 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 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 concrete curl commands, request/response examples, or copy-paste ready code snippets. The workflow is procedural but abstract ('Load the schema, discover endpoints'). | 2 / 3 |
Workflow Clarity | The 5-step 'How To Use' section provides a reasonable sequence, but lacks validation checkpoints or feedback loops. There's no guidance on what to do if schema loading fails, if the API returns unexpected responses, or how to verify a successful swap quote before proceeding to execution. | 2 / 3 |
Progressive Disclosure | Clear structure with a concise overview in the main file and well-signaled one-level-deep references to `references/openapi.yaml` and `references/OPENAPI.md`. Content is appropriately split between the skill file and reference materials. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%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
Table of Contents
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.