Raydium - swaps, CLMM positions, AMM liquidity on Solana
70
59%
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/raydium/SKILL.mdQuality
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear niche (Raydium DEX on Solana) with distinct protocol-specific terminology, making it unlikely to conflict with other skills. However, it lacks explicit trigger guidance ('Use when...') and relies heavily on technical jargon without explaining concrete user-facing actions, which limits its effectiveness for skill selection.
Suggestions
Add a 'Use when...' clause specifying trigger scenarios like 'Use when the user wants to swap tokens on Raydium, manage liquidity positions, or interact with Raydium pools on Solana'
Expand technical abbreviations and add user-friendly terms: 'token swaps, concentrated liquidity (CLMM) positions, AMM liquidity pools, DEX trading'
Include concrete actions: 'Create and manage CLMM positions, add/remove AMM liquidity, execute token swaps on Raydium'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Raydium on Solana) and lists some actions (swaps, CLMM positions, AMM liquidity), but uses abbreviated/technical terms without explaining concrete actions like 'create', 'manage', or 'monitor'. | 2 / 3 |
Completeness | Only addresses 'what' at a high level with no 'Use when...' clause or explicit trigger guidance. Missing any indication of when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Raydium', 'swaps', 'Solana', 'CLMM', 'AMM', and 'liquidity', but these are fairly technical. Missing common user phrases like 'trade tokens', 'provide liquidity', 'liquidity pool', or 'DEX'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche - Raydium is a distinct protocol on Solana. The combination of 'Raydium', 'CLMM', and 'Solana' creates clear, unique triggers unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
79%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, actionable skill that efficiently documents Raydium DEX operations with concrete commands, tools, and executable code examples. The main weaknesses are the lack of explicit validation/verification steps for financial operations and the monolithic structure that could benefit from splitting advanced content into separate files.
Suggestions
Add explicit validation steps for financial operations (e.g., 'Verify transaction signature before proceeding', 'Check position state after liquidity changes')
Split detailed API reference and CLMM strategy guidance into separate files (e.g., CLMM_GUIDE.md, API_REFERENCE.md) with clear links from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, presenting commands, tools, and code examples without explaining basic concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples, specific CLI commands with real parameters, and concrete tool names. The code is copy-paste ready with actual mint addresses and realistic parameter values. | 3 / 3 |
Workflow Clarity | The CLMM Position Management section outlines steps but lacks explicit validation checkpoints. For financial operations involving liquidity and swaps, there should be verification steps (e.g., check transaction success, validate position state before closing). | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but everything is inline in one file. For a skill this comprehensive (150+ lines), advanced topics like CLMM strategies or detailed API reference could be split into separate files with clear navigation. | 2 / 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 | |
2a8c94e
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.