CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

trading-evm

Trade tokens on EVM chains - Uniswap V3, 1inch on Ethereum, Arbitrum, Optimism, Base, Polygon

60

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/trading-evm/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 highly actionable with executable code and clear command/API coverage, but it is a single monolithic reference rather than a progressive overview, and it lacks an explicit validate-then-execute workflow for irreversible swaps.

Suggestions

Add an explicit recommended workflow (e.g., 1. /quote to preview, 2. confirm expected output and price impact, 3. execute swap, 4. verify transaction hash and balance) with a feedback loop for slippage/insufficient-balance errors.

Move the full TypeScript API reference, token-address tables, and per-chain examples into separate files under references/ and keep SKILL.md as a concise overview with one-level-deep links.

Collapse the five near-identical 'Chain-Specific Examples' into one parameterized example plus a chain table to reduce redundancy.

DimensionReasoningScore

Conciseness

Mostly lean reference content built from code and tables that assumes Claude's competence, but the 'Chain-Specific Examples' section repeats near-identical swap patterns across five chains and could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready TypeScript covering quotes, swaps, token resolution, balances, route comparison, and error handling with concrete examples for the common cases.

5 / 5

Workflow Clarity

A /quote command exists, but for irreversible real-fund swaps there is no explicit sequenced validate-quote-then-execute-then-confirm workflow with error-recovery checkpoints, so the destructive-operation cap of 3 applies.

3 / 5

Progressive Disclosure

No bundle files exist and the entire API reference, token-address tables, and per-chain examples are inlined in one ~330-line file; section headers provide structure, but content that belongs in separate reference files is inline.

3 / 5

Total

15

/

20

Passed

Description

70%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 is specific and distinctive, clearly communicating a narrow EVM DEX-trading niche. Its main weakness is the absence of any explicit 'when to use' trigger guidance.

Suggestions

Add a 'Use when...' clause naming natural trigger phrases (e.g., 'Use when the user wants to swap, trade, or buy tokens on Ethereum, Arbitrum, Optimism, Base, or Polygon').

Include common synonyms like 'swap' and 'DEX' alongside 'trade tokens' to improve trigger-term coverage.

Mention quote/compare/balance capabilities briefly so the 'what' reflects the full command surface, not just swaps.

DimensionReasoningScore

Specificity

Names the concrete action ('Trade tokens') plus specific DEXes (Uniswap V3, 1inch) and five named chains, listing several specific venues with only minor gaps in coverage.

4 / 5

Completeness

The 'what' is clear (trade tokens on EVM chains via Uniswap V3/1inch), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('trade', 'tokens', 'EVM') plus concrete chain and DEX names, but omits common synonyms like 'swap', 'crypto', or 'DEX'.

4 / 5

Distinctiveness Conflict Risk

A clear niche — EVM DEX trading on named chains with named aggregators — with distinct triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

16

/

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.

Validation — 15 / 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

Path

src/skills/bundled/trading-evm/SKILL.md

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.