dex
Cross-chain DEX market intelligence - trending tokens, gainers, losers, volume, stats across all chains and protocols
85
77%
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 ./src/skills/bundled/dex/SKILL.mdQuality
Discovery
54%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 effectively identifies its crypto/DeFi niche with good trigger terms that users would naturally use. However, it reads more like a feature list than an actionable skill description - it lacks concrete action verbs and completely omits guidance on when Claude should select this skill. The missing 'Use when...' clause is a significant gap for skill selection.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about DEX prices, token trends, market movers, or cross-chain trading data'
Convert data categories into action verbs: 'Fetches trending tokens, identifies top gainers/losers, retrieves volume statistics' instead of just listing data types
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (DEX market intelligence) and lists data types (trending tokens, gainers, losers, volume, stats), but these are more like data categories than concrete actions. Missing verbs describing what Claude actually does with this data (fetch, analyze, compare, etc.). | 2 / 3 |
Completeness | Describes what data is available but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance should cap completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'DEX', 'trending tokens', 'gainers', 'losers', 'volume', 'cross-chain', 'protocols'. These are terms crypto users naturally use when seeking market data. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche in crypto/DeFi space with specific focus on cross-chain DEX data. The combination of 'DEX', 'cross-chain', and specific metrics (gainers, losers, trending) creates a distinct trigger profile unlikely to conflict with other skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that exemplifies good practices. It's highly concise, immediately actionable with concrete commands and examples, and well-organized with clear tables and sections. The content assumes Claude's competence and focuses purely on the specific commands and filters needed to use the DexScreener integration.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what DEXes are or how they work. Every section delivers actionable information with minimal prose. Tables and code blocks maximize information density. | 3 / 3 |
Actionability | Fully concrete with copy-paste ready commands. Clear command syntax, specific filter options in a table, and multiple practical examples showing exact usage patterns. No vague descriptions. | 3 / 3 |
Workflow Clarity | This is a simple query-based skill with no multi-step processes or destructive operations. Commands are single actions with clear inputs and outputs. The structure makes it unambiguous what each command does. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections: discovery commands, token data commands, and available data fields. Content is appropriately sized for a single file (~80 lines). No need for external references given the scope. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- alsk1992/CloddsBot
- Commit
2a8c94e
- 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.