analyzing-liquidity-pools
Analyze DEX liquidity pools for TVL, volume, fees, impermanent loss, and LP profitability. Use when analyzing liquidity pools, calculating impermanent loss, or comparing DEX pools. Trigger with phrases like "analyze liquidity pool", "calculate impermanent loss", "LP returns", "pool TVL", "DEX pool metrics", or "compare pools".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill analyzing-liquidity-pools84
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 a well-crafted skill description that excels across all dimensions. It provides specific capabilities (TVL, volume, fees, impermanent loss, LP profitability analysis), includes comprehensive natural trigger terms that DeFi users would actually say, and clearly delineates both what the skill does and when to use it. The domain-specific terminology creates a distinct niche with minimal conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Analyze DEX liquidity pools for TVL, volume, fees, impermanent loss, and LP profitability.' These are concrete, measurable metrics and analyses. | 3 / 3 |
Completeness | Clearly answers both what (analyze pools for TVL, volume, fees, IL, profitability) AND when (explicit 'Use when...' clause plus 'Trigger with phrases like...' providing concrete trigger guidance). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'analyze liquidity pool', 'calculate impermanent loss', 'LP returns', 'pool TVL', 'DEX pool metrics', 'compare pools'. These are terms DeFi users naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche in DeFi/DEX liquidity pool analysis with distinct domain-specific triggers like 'impermanent loss', 'LP returns', 'DEX pool metrics' that are unlikely to conflict with general finance or other 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 skill provides strong actionable guidance with executable CLI commands and clear output examples. The structure and progressive disclosure are well-handled. However, it could be more concise by removing the Prerequisites section and external Resources, and would benefit from explicit validation steps for verifying analysis results.
Suggestions
Remove the Prerequisites section - Claude already understands Python requirements and LP concepts
Add validation steps after analysis commands (e.g., 'Verify TVL is non-zero and within expected range before proceeding')
Remove the external Resources section - these URLs don't add actionable value to the skill execution
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary content like the Prerequisites section explaining concepts Claude already knows, and the Resources section with external links that add little value for execution. | 2 / 3 |
Actionability | Provides fully executable CLI commands with specific flags and arguments. Commands are copy-paste ready with clear parameter examples for pool addresses, token pairs, and output formats. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks validation checkpoints. No feedback loops for error recovery - the error handling section just lists issues without recovery steps. For financial analysis tools, validation of results would be valuable. | 2 / 3 |
Progressive Disclosure | Well-structured with clear overview, appropriately references external files for errors and examples (one level deep), and organizes content into logical sections. The main skill stays focused while pointing to detailed references. | 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 | |
- 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.