Find and compare DeFi yield opportunities across protocols with APY calculations, risk assessment, and optimization recommendations. Use when searching for yield farming opportunities, comparing DeFi protocols, or analyzing APY/APR rates. Trigger with phrases like "find DeFi yields", "compare APY", "best yield farming", "optimize DeFi returns", "stablecoin yields", or "liquidity pool rates".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill optimizing-defi-yields84
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 an excellent skill description that hits all the marks. It provides specific capabilities (yield comparison, APY calculations, risk assessment), comprehensive trigger terms covering natural user language, and explicit guidance on when to use the skill. The DeFi-specific terminology creates a clear, distinctive niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Find and compare DeFi yield opportunities', 'APY calculations', 'risk assessment', and 'optimization recommendations'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (find/compare yields, APY calculations, risk assessment, optimization) AND when with explicit 'Use when...' clause and dedicated 'Trigger with phrases like...' section providing concrete examples. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural user terms including 'DeFi yields', 'compare APY', 'yield farming', 'optimize DeFi returns', 'stablecoin yields', 'liquidity pool rates', and 'APY/APR rates'. These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on DeFi yield farming with domain-specific triggers like 'APY', 'yield farming', 'liquidity pool rates', and 'stablecoin yields'. Unlikely to conflict with general finance or crypto skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent actionability - every command is executable and clearly documented with expected outputs. The main weaknesses are some unnecessary explanatory content (Prerequisites, Overview) and missing validation steps for what could be time-sensitive financial data. The progressive disclosure is handled well with appropriate external references.
Suggestions
Remove the Prerequisites section - Claude already understands DeFi concepts and Python requirements
Add validation steps to verify data freshness before making yield recommendations (e.g., check cache age, confirm API response timestamps)
Trim the Overview section which largely duplicates the skill description
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary content like the Prerequisites section explaining DeFi concepts Claude already knows, and the Overview restates what's in the description. However, the command examples themselves are efficient and well-structured. | 2 / 3 |
Actionability | Provides fully executable bash commands with clear flags and options. Every step has copy-paste ready commands with specific parameters, and the output examples show exactly what to expect. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but there are no validation checkpoints or feedback loops. For financial/DeFi operations, there should be verification steps to confirm data freshness or validate results before acting on yield recommendations. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate use of external references (errors.md, examples.md) that are one level deep and clearly signaled. Quick examples inline with detailed examples referenced externally. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
Table of Contents
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.