openocean
OpenOcean DEX aggregator. Best swap rates across 25+ blockchains with cross-chain support.
45
48%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xterrybit/openocean/SKILL.mdQuality
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 identifies the domain (OpenOcean DEX aggregation) and hints at capabilities but lacks concrete actions and completely omits explicit trigger guidance ('Use when...'). It reads more like a marketing tagline than a functional skill description, making it difficult for Claude to reliably select this skill at the right time.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user wants to swap tokens, find best DEX rates, trade across chains, or mentions OpenOcean.'
List specific concrete actions such as 'Execute token swaps, compare rates across DEXes, perform cross-chain bridges, get price quotes.'
Include natural user terms like 'token swap', 'trade crypto', 'DeFi', 'bridge tokens', 'exchange', and specific blockchain names to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (DEX aggregation) and mentions some capabilities ('swap rates', 'cross-chain support', '25+ blockchains'), but doesn't list specific concrete actions like executing swaps, comparing rates, bridging tokens, etc. | 2 / 3 |
Completeness | Describes what it does at a high level (DEX aggregation, 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 weak, so this scores 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'swap', 'DEX', 'cross-chain', and 'blockchains' that users might say, but misses common variations like 'token swap', 'trade', 'exchange tokens', 'bridge', specific chain names, or 'DeFi'. | 2 / 3 |
Distinctiveness Conflict Risk | Mentioning 'OpenOcean' specifically and 'DEX aggregator' provides some distinctiveness, but the generic 'swap rates across blockchains' could overlap with other DeFi or blockchain trading skills. | 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 excellent actionable API examples with concrete, executable curl commands covering quotes, swaps, cross-chain, and utility endpoints. However, it lacks a clear end-to-end workflow for the critical quote→approve→swap sequence with validation checkpoints, which is important for financial operations. The content is somewhat bloated by the full chains table, feature list, and referral fee explanation that could be trimmed or externalized.
Suggestions
Add an explicit numbered workflow for the full swap lifecycle: 1) Get quote → 2) Check balance → 3) Check/set token allowance → 4) Get swap_quote → 5) Display details to user → 6) Execute only after confirmation, with validation at each step.
Move the 25-row supported chains table to a separate CHAINS.md reference file and keep only the most common 5-6 chains inline.
Remove the features bullet list and the explanatory text about referral fees (e.g., 'OpenOcean allows up to 3%') — these don't help Claude execute tasks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The supported chains table (25 rows) and referral fee section add significant bulk. The features bullet list is unnecessary filler Claude doesn't need. However, the API examples themselves are lean and well-structured. | 2 / 3 |
Actionability | All API calls are fully executable curl commands with proper variable substitution, jq parsing, and concrete token addresses/amounts. The examples are copy-paste ready with clear parameterization. | 3 / 3 |
Workflow Clarity | The safety rules mention checking allowance, verifying addresses, and confirming with users, but there's no explicit workflow sequence tying quote → approval → swap together with validation checkpoints. For a financial operation involving destructive/irreversible transactions, the lack of a clear step-by-step flow with feedback loops is a gap. | 2 / 3 |
Progressive Disclosure | Everything is in a single monolithic file with no bundle files. The supported chains table and error handling could be split into reference files. Links to external docs are provided but internal structure is flat with no layered navigation. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%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
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.