CtrlK
BlogDocsLog inGet started
Tessl Logo

defi-yield

DeFi yield analysis and optimization — lending rates, LP yields, staking returns, yield farming strategies, risk-adjusted yield comparison, and protocol-level sustainability assessment.

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/defi-yield/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

A thorough, actionable DeFi yield reference with executable code and concrete output guidance, but it is a monolithic file that explains some known concepts and lacks an explicit sequenced analysis workflow with validation checkpoints. Tightening known-concept explanations, adding a procedural workflow, and splitting into referenced files would raise the weaker dimensions.

Suggestions

Add an explicit sequenced workflow (e.g. 1. pull rates from DeFiLlama, 2. compute net/IL-adjusted yields, 3. assess sustainability, 4. rank risk-adjusted) with validation checkpoints before producing the final output.

Trim explanations of concepts Claude already knows — such as the impermanent-loss definition and the 'smart contract risk is the dominant risk' note — to reclaim token budget.

Split the monolithic body into one-level-deep referenced files (e.g. references/protocols.md, references/output-template.md) so SKILL.md serves as a lean overview with clear navigation.

DimensionReasoningScore

Conciseness

The tables and executable functions are token-efficient, but the body also explains concepts Claude already knows (e.g. defining impermanent loss as 'the core risk of LP positions' and the Note that 'Smart contract risk is the dominant risk in DeFi'), so it could be tightened.

2 / 3

Actionability

It provides complete, copy-paste-ready Python functions (impermanent_loss, net_lp_yield, yield_sustainability, risk_adjusted_yield) plus a concrete output-format template and a data-source table with access details.

3 / 3

Workflow Clarity

Content is organized into topical sections (1–6) and ends with an output template, but there is no explicit procedural sequence (gather → compute → assess → rank) and no validation checkpoints for the multi-faceted analysis.

2 / 3

Progressive Disclosure

The ~260-line body is a single monolithic file with no references/, scripts/, or assets/ bundle; it is well-sectioned but content that could be split (protocol reference, output templates) is inline, and it exceeds the 50-line simple-skill exception.

2 / 3

Total

9

/

12

Passed

Description

72%

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

A specific, well-targeted DeFi yield description with strong natural trigger terms and clear distinctiveness, held back only by a missing explicit 'Use when' trigger clause and action verbs that stay at the generic 'analysis and optimization' level. Adding a usage trigger and more concrete verbs would lift the weaker dimensions.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when analyzing DeFi yields, comparing protocol APYs, assessing yield sustainability, or planning yield farming strategies.'

Replace the generic 'analysis and optimization' with concrete verbs such as 'compute', 'compare', 'rank', and 'assess' to strengthen capability specificity.

DimensionReasoningScore

Specificity

It names the DeFi-yield domain and enumerates six subtopics ('lending rates, LP yields, staking returns, yield farming strategies, risk-adjusted yield comparison, and protocol-level sustainability assessment'), but the only action verbs are the generic 'analysis and optimization' rather than multiple concrete actions.

2 / 3

Completeness

It clearly answers 'what' the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

Natural user-facing terms are well covered — 'DeFi yield', 'yield farming', 'LP yields', 'staking returns', and 'lending rates' are exactly the phrasings someone researching DeFi yields would say.

3 / 3

Distinctiveness Conflict Risk

The narrow DeFi-yield niche ('yield farming strategies', 'protocol-level sustainability assessment') is clearly distinguishable from other skills and unlikely to trigger for the wrong one.

3 / 3

Total

10

/

12

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
HKUDS/Vibe-Trading
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.