OpenOcean DEX aggregator. Best swap rates across 25+ blockchains with cross-chain support.
71
Quality
60%
Does it follow best practices?
Impact
Pending
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 specific product (OpenOcean) and its core function (DEX aggregation for swaps), but lacks explicit trigger guidance and specific actionable capabilities. It would benefit from a 'Use when...' clause and more concrete action verbs describing what operations Claude can perform with this skill.
Suggestions
Add a 'Use when...' clause with trigger terms like 'swap tokens', 'find best rates', 'cross-chain transfer', 'DEX trade', or 'OpenOcean'
List specific concrete actions such as 'Execute token swaps, compare rates across DEXs, perform cross-chain bridges, check liquidity'
Include common user phrases like 'trade crypto', 'exchange tokens', 'bridge assets', or specific blockchain names users might mention
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (DEX aggregator, swaps, blockchains) and mentions 'best swap rates' and 'cross-chain support', but doesn't list specific concrete actions like 'execute swaps', 'compare rates', 'bridge tokens', etc. | 2 / 3 |
Completeness | Describes what it is (DEX aggregator with swap rates) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'DEX', 'swap', 'blockchains', 'cross-chain', but misses common user variations like 'token exchange', 'trade', 'bridge', specific chain names, or 'crypto swap'. | 2 / 3 |
Distinctiveness Conflict Risk | 'OpenOcean' is a specific product name which helps distinctiveness, but 'DEX aggregator' and 'swap' could overlap with other crypto/DeFi skills without clearer trigger boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill with excellent actionability and conciseness. The curl examples are complete and executable, and the chain/error reference tables add value. The main weakness is the lack of explicit validation workflows for financial operations - the safety rules are listed but not integrated into a step-by-step process with checkpoints.
Suggestions
Add an explicit workflow section showing the complete swap process: 1) Get quote 2) Verify price impact 3) Check/set allowance 4) Get swap tx 5) Confirm with user 6) Execute - with validation at each step
Include a concrete example of checking token allowance and approving if needed before the swap transaction
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information. No unnecessary explanations of what DEX aggregation is or how blockchains work - it assumes Claude's competence and jumps straight to actionable content. | 3 / 3 |
Actionability | Excellent executable examples throughout with complete curl commands, proper variable setup, and jq parsing. All code is copy-paste ready with clear parameter explanations in the table format. | 3 / 3 |
Workflow Clarity | Safety rules are listed but lack explicit validation checkpoints in the workflow. For financial operations involving swaps, there should be explicit steps like 'get quote -> verify output -> check allowance -> execute' with validation between each step. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from basic quotes to cross-chain swaps. External links to docs are provided for deeper reference. Content is appropriately structured for a single SKILL.md file without needing additional files. | 3 / 3 |
Total | 11 / 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 | |
45f9fac
Table of Contents
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.