Meteora DLMM - dynamic liquidity market maker on Solana
56
47%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/meteora/SKILL.mdQuality
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 a label rather than a functional skill description. It identifies the domain (Meteora DLMM on Solana) but fails to describe any concrete actions the skill performs and completely lacks trigger guidance for when Claude should select it. It needs substantial expansion to be useful for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates and manages DLMM liquidity positions, configures bin strategies, monitors pool performance, and handles deposits/withdrawals on Meteora.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Meteora DLMM pools, liquidity positions, bin strategies, LP management, or Solana DeFi liquidity provisioning.'
Include common user-facing keywords and variations such as 'liquidity pool', 'LP', 'bins', 'concentrated liquidity', 'DeFi', and 'SOL' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Meteora DLMM on Solana) but does not describe any concrete actions. It reads more like a label or title than a capability description—there are no verbs indicating what the skill actually does. | 1 / 3 |
Completeness | The description only vaguely addresses 'what' (it's about Meteora DLMM) and completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent trigger guidance, and the 'what' itself is not actionable. | 1 / 3 |
Trigger Term Quality | It includes some relevant keywords like 'Meteora', 'DLMM', 'dynamic liquidity market maker', and 'Solana' that a user familiar with the ecosystem might use. However, it misses common variations and related terms like 'liquidity pool', 'LP', 'swap', 'bin', 'position', or 'DeFi'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Meteora DLMM' and 'Solana' provides some niche specificity, but without concrete actions it could overlap with other Solana DeFi or general liquidity-related skills. The domain terms help but the lack of action specificity weakens distinctiveness. | 2 / 3 |
Total | 6 / 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 concise, well-structured skill that efficiently communicates command syntax for Meteora DLMM operations. However, it lacks important workflow guidance around swap safety (e.g., quote before swap, slippage settings, transaction confirmation) and provides no information about expected outputs or error handling, which are critical for financial operations on-chain.
Suggestions
Add a recommended workflow showing quote → confirm → swap sequence with validation checkpoints, especially since swaps are destructive/irreversible financial operations
Include expected output examples for each command so Claude knows what a successful response looks like versus an error
Add key parameters like slippage tolerance, and guidance on error scenarios (insufficient balance, pool not found, transaction failure)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what DLMM is or how Solana works. Every line serves a purpose. | 3 / 3 |
Actionability | Provides concrete command syntax and examples, but lacks details on what happens after commands are run (expected output, error handling), and there's no executable code or implementation details for how these commands actually work. | 2 / 3 |
Workflow Clarity | Commands are listed clearly but there's no workflow for multi-step processes like checking a quote before executing a swap, no validation steps (e.g., confirming transaction details before signing), and no error recovery guidance for failed transactions on Solana. | 2 / 3 |
Progressive Disclosure | For a simple, short skill under 50 lines with a single-purpose focus, the content is well-organized with clear sections for commands and examples. No need for external references given the scope. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%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 | |
e71a5f6
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.