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)
Install with Tessl CLI
npx tessl i github:Demerzels-lab/elsamultiskillagent --skill sushiswap-api89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 90%
↑ 1.38xAgent success when using this skill
Validation for skill structure
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 capabilities, includes natural trigger terms users would use, explicitly states when to use it with a clear 'Use this skill when' clause, and distinguishes itself from related skills (particularly the Javascript API variant). The description is comprehensive yet focused.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'token swapping', 'swap quoting', 'pricing', 'executable transaction generation', 'fetch token prices', 'retrieve token metadata', 'discover supported AMM liquidity sources'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (REST API for token swapping, quoting, pricing) AND when with explicit 'Use this skill when the user wants to:' clause followed by specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'swap quote', 'token prices', 'swap transaction', 'SushiSwap', 'evm networks', 'REST', 'HTTP', 'AMM', 'liquidity sources'. Also explicitly distinguishes from 'Javascript API' to prevent confusion. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically SushiSwap Aggregator, REST/HTTP API (not Javascript), 40+ EVM networks. The explicit exclusion of 'SushiSwap Javascript API' further reduces conflict risk with related skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-structured and concise, appropriately delegating detailed API specifications to the OpenAPI schema file. However, it lacks concrete executable examples (curl commands, code snippets) that would make it immediately actionable, and the workflow could benefit from explicit validation checkpoints integrated with the error handling guidance.
Suggestions
Add 1-2 concrete curl or Python examples showing a complete quote request with the required referrer parameter
Integrate error handling into the workflow as explicit validation/retry steps (e.g., 'If 422: check parameters against schema; If 529: wait 2s and retry')
Include a minimal working example showing the full flow from loading the schema to making a successful request
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows (like what REST APIs are or how HTTP works). Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | The skill provides clear procedural guidance and references the OpenAPI schema, but lacks concrete executable code examples (e.g., curl commands or Python requests). The 'How To Use' section describes steps abstractly rather than showing copy-paste ready examples. | 2 / 3 |
Workflow Clarity | The 5-step workflow in 'How To Use' provides a clear sequence, but lacks explicit validation checkpoints or feedback loops. Error handling is mentioned separately but not integrated into the workflow with retry logic or validation steps. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear one-level-deep references to the OpenAPI schema and OPENAPI.md guidance file. The main skill serves as a concise overview with well-signaled navigation to detailed materials. | 3 / 3 |
Total | 10 / 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.
- 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.