meteora
Meteora DLMM - dynamic liquidity market maker on Solana
Overall
score
61%
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
22%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 description is essentially just a label rather than a functional skill description. It identifies the technology (Meteora DLMM on Solana) but fails to explain what actions the skill performs or when Claude should select it. Without concrete capabilities and explicit trigger guidance, Claude cannot effectively choose this skill from a pool of alternatives.
Suggestions
Add specific actions the skill performs, e.g., 'Create and manage DLMM liquidity pools, set bin configurations, deposit/withdraw liquidity, analyze fee earnings'
Add an explicit 'Use when...' clause with trigger terms like 'Meteora', 'DLMM', 'liquidity pool on Solana', 'bin step', 'concentrated liquidity'
Include common user phrasings such as 'LP position', 'provide liquidity', 'Solana DeFi', or 'dynamic AMM' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('dynamic liquidity market maker on Solana') but provides no concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'create pools', 'manage liquidity', or 'analyze positions'. | 1 / 3 |
Completeness | The description only partially answers 'what' (it's a DLMM on Solana) and completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent trigger guidance, and the 'what' is too vague to be useful. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('Meteora', 'DLMM', 'Solana', 'liquidity market maker') that users familiar with the domain might use, but misses common variations like 'LP', 'liquidity pool', 'DeFi', or action-oriented terms users would naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | The specific mention of 'Meteora DLMM' and 'Solana' provides some distinctiveness from generic DeFi or liquidity skills, but without clear action triggers, it could still overlap with other Solana DeFi or liquidity-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is admirably concise and well-structured for its scope, but lacks actionability details that would help Claude execute reliably. The financial nature of swaps warrants at least basic error handling guidance and expected output formats. The command syntax is clear but incomplete without parameter constraints.
Suggestions
Add expected output format for each command (e.g., what does a quote response look like)
Include basic error handling guidance for failed swaps or invalid tokens
Specify valid parameter formats (e.g., amount decimals, supported token symbols)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean - only 12 lines of content with zero unnecessary explanation. Assumes Claude knows what DLMM and Solana are, every token earns its place. | 3 / 3 |
Actionability | Commands are concrete and copy-paste ready, but lacks details on expected outputs, error handling, or what parameters are valid (e.g., supported tokens, amount formats). | 2 / 3 |
Workflow Clarity | For a simple skill, the commands are clear, but there's no guidance on workflow (e.g., should you quote before swap? What if swap fails?). Missing validation for financial operations. | 2 / 3 |
Progressive Disclosure | For a skill this simple (under 50 lines, single-purpose), the flat structure with commands and examples is appropriate. No need for external references. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
91%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 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.