CtrlK
BlogDocsLog inGet started
Tessl Logo

defi

DeFi protocol interactions. Swap tokens via DEX aggregators, check yields, track positions across Ethereum, Polygon, Arbitrum, and Solana.

82

Quality

77%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/0xterrybit/defi/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid description with strong specificity and clear domain focus in DeFi. The main weakness is the absence of explicit 'Use when...' guidance, which limits Claude's ability to know exactly when to select this skill. Adding trigger phrases and common user terminology variations would improve selection accuracy.

Suggestions

Add a 'Use when...' clause with trigger scenarios like 'Use when user asks about token swaps, yield farming, DeFi positions, or mentions specific chains like Ethereum or Solana'

Include common user terminology variations such as 'trade', 'APY', 'liquidity pools', 'farming', 'staking', or 'bridge tokens' to improve trigger term coverage

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'Swap tokens via DEX aggregators, check yields, track positions' with specific chains named (Ethereum, Polygon, Arbitrum, Solana).

3 / 3

Completeness

Clearly answers 'what' with specific DeFi actions and supported chains, but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill.

2 / 3

Trigger Term Quality

Includes relevant terms like 'DeFi', 'swap tokens', 'DEX', 'yields', and chain names, but missing common variations users might say like 'trade', 'liquidity', 'APY', 'farming', or 'bridge'.

2 / 3

Distinctiveness Conflict Risk

Clear niche in DeFi/crypto space with distinct triggers like 'DEX aggregators', 'yields', 'positions', and specific blockchain names that are unlikely to conflict with non-crypto skills.

3 / 3

Total

10

/

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-crafted skill that provides comprehensive DeFi interaction capabilities with excellent actionability and token efficiency. The curl commands are complete and executable, tables provide quick reference, and safety rules establish clear boundaries. The main gap is the lack of explicit validation/retry workflows for transaction execution and error recovery beyond the basic error table.

Suggestions

Add explicit validation steps after transaction submission (e.g., checking transaction hash, waiting for confirmation, verifying final balances)

Include a feedback loop for handling failed transactions: check status → diagnose error → adjust parameters → retry

DimensionReasoningScore

Conciseness

The skill is lean and efficient, providing direct commands and code without explaining basic concepts like what DeFi is or how APIs work. Every section delivers actionable content with minimal preamble.

3 / 3

Actionability

Fully executable curl commands with proper variable setup, complete API endpoints, and jq parsing. Commands are copy-paste ready with clear configuration variables at the top of each section.

3 / 3

Workflow Clarity

The Example Interactions section shows the workflow pattern (quote → display → confirm → execute), and Safety Rules mention verification steps, but there's no explicit validation checkpoint for checking transaction success or handling failed transactions in a retry loop.

2 / 3

Progressive Disclosure

Well-organized with clear sections (Quick Commands, Swap Tokens, Cross-Chain, etc.), reference tables for chains and APIs, and external links for deeper exploration. Content is appropriately structured for a single SKILL.md file.

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.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

9

/

11

Passed

Repository
Demerzels-lab/elsamultiskillagent
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.