dex
Cross-chain DEX market intelligence - trending tokens, gainers, losers, volume, stats across all chains and protocols
66
58%
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 targets a clear niche in cross-chain DEX market data and uses strong domain-specific trigger terms that crypto users would naturally employ. However, it lacks explicit trigger guidance ('Use when...') and reads more as a list of data categories rather than concrete actions the skill performs, weakening its completeness and specificity.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about DEX token prices, market trends, top gainers/losers, or trading volume across blockchains.'
Rewrite with action verbs in third person to clarify concrete capabilities, e.g., 'Fetches and displays trending tokens, top gainers/losers, and trading volume from decentralized exchanges across multiple blockchains.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists several data types (trending tokens, gainers, losers, volume, stats) which gives a sense of capabilities, but these are more like data categories than concrete actions. It doesn't specify what actions are performed (e.g., 'fetches', 'analyzes', 'compares', 'generates reports'). | 2 / 3 |
Completeness | Describes what (market intelligence data types) 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 only moderately clear, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Contains strong natural keywords users would say: 'DEX', 'trending tokens', 'gainers', 'losers', 'volume', 'cross-chain', 'protocols', 'stats'. These are terms a crypto user would naturally use when seeking market data. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'cross-chain DEX market intelligence' is a very specific niche. It's unlikely to conflict with other skills given the specialized crypto/DeFi domain focus with explicit mention of DEX, chains, and protocols. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a clear reference for DEX market intelligence slash commands with good examples and organized sections. Its main weakness is that it's unclear whether these slash commands map to actual tool implementations or are just conceptual - there's no underlying API call structure, tool use specification, or code. The content is well-organized for a reference card but slightly verbose in places like the trigger phrase list.
Suggestions
Add concrete implementation details: show the actual DexScreener API endpoints being called (e.g., `https://api.dexscreener.com/latest/dex/tokens/{address}`) so Claude knows how to execute these commands
Trim the 'Use this skill when users ask about' section - Claude can infer intent from the command descriptions; a 1-2 line summary would suffice
Consider adding a brief example of the response format/output so Claude knows how to present the data back to users
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity - the long trigger phrase list ('Use this skill when users ask about') could be trimmed, and the filter table, while useful, is somewhat lengthy. The 'Data Available Per Token' section at the end is a simple list that earns its place, but overall there's room to tighten. | 2 / 3 |
Actionability | The commands are clearly specified with examples, which is good. However, these are slash commands for a custom tool/integration, and there's no indication of what actually happens under the hood - no API endpoints, no code, no tool definitions. If the slash commands are the interface, they're concrete enough, but there's no executable code or implementation detail showing how these commands resolve. | 2 / 3 |
Workflow Clarity | This is a simple, single-purpose skill (querying market data) with no destructive or multi-step operations. The commands are clearly organized into discovery vs. token-specific categories, and the examples make the usage unambiguous. No validation steps are needed for read-only data queries. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections (Discovery Commands, Token Data Commands, Data Available), but everything is inline in a single file. The filter table and extensive examples could potentially be split out for a cleaner overview. However, at ~80 lines it's borderline - not egregiously long but could benefit from better separation. | 2 / 3 |
Total | 9 / 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
e71a5f6
- 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.