CtrlK
BlogDocsLog inGet started
Tessl Logo

dex

Cross-chain DEX market intelligence - trending tokens, gainers, losers, volume, stats across all chains and protocols

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/dex/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean, concrete, and well-structured, with copy-paste-ready commands and examples that make the skill immediately actionable. It is a clean simple-skill reference with no padding.

DimensionReasoningScore

Conciseness

The body is efficient and command-focused with no concept explanation Claude would already know; only minor repetition between command listings and examples keeps it from a 5.

4 / 5

Actionability

Concrete copy-paste-ready slash commands with worked examples (e.g., '/dex trending solana', '/dex price SOL', '/dex token <address> [chain]') cover the common cases fully.

5 / 5

Workflow Clarity

This is a simple single-purpose, read-only query skill with unambiguous commands and no destructive/batch operations, so the simple-skill exception applies and the action is fully clear.

5 / 5

Progressive Disclosure

Content is well-organized into clear sections (Discovery Commands, Token Data Commands, Data Available Per Token) with tables and is self-contained with no nested references, though at ~85 lines it sits just outside the under-50-line simple-skill exception.

4 / 5

Total

18

/

20

Passed

Description

66%Weight 40%Scale 1-5

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 clearly names a specific niche and several concrete data categories but lacks an explicit trigger ("Use when...") clause, capping completeness at 3. Trigger terms are natural but could be broadened with synonyms.

Suggestions

Add an explicit 'Use when...' clause to the frontmatter description (e.g., 'Use when users ask about token prices, trending coins, gainers/losers, or DEX volume across chains') to lift completeness above 3.

Convert the data-category noun list into concrete actions with verbs (e.g., 'Fetch trending tokens, look up token prices, compare gainers and losers across chains') to strengthen specificity.

Add common synonyms users say — 'pumping', 'hot', 'movers', 'price' — to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete capability areas — "trending tokens, gainers, losers, volume, stats" — but as a noun list rather than explicit actions, leaving minor coverage gaps.

4 / 5

Completeness

The "what" is clear (cross-chain DEX market intelligence with listed data types), but there is no "Use when..." trigger clause in the frontmatter description, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Natural user terms like "trending", "gainers", "losers", and "volume" are present, though common synonyms (e.g., "pumping", "price", "movers", "hot") that appear in the body are missing from the description.

4 / 5

Distinctiveness Conflict Risk

"Cross-chain DEX market intelligence" carves a clear niche with distinct triggers, with only minor overlap risk against a generic price/market skill.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
alsk1992/CloddsBot
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.