Solana wallet management and token trading via Jupiter aggregator. Check balances, view transaction history, swap tokens, and manage your Solana portfolio.
77
Quality
72%
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 ./public/skills/0xterrybit/solana-trader/SKILL.mdQuality
Discovery
67%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 effectively communicates specific capabilities for Solana wallet management and clearly identifies its niche (Jupiter aggregator integration). However, it lacks explicit trigger guidance ('Use when...') and could benefit from additional natural keywords users might employ when seeking this functionality.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user asks about Solana tokens, SOL balance, swapping on Jupiter, or managing crypto portfolio'
Include common keyword variations users might say: 'SOL', 'trade', 'exchange', 'DeFi', 'crypto wallet', '.sol'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Check balances, view transaction history, swap tokens, and manage your Solana portfolio.' These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied through the capability list. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Solana', 'wallet', 'Jupiter', 'balances', 'swap tokens', but missing common variations users might say like 'SOL', 'trade', 'exchange', 'crypto', or 'DeFi'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: Solana-specific wallet management via Jupiter aggregator. Unlikely to conflict with general crypto skills or other blockchain-specific tools due to explicit Solana and Jupiter mentions. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%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-crafted, highly actionable skill with excellent workflow clarity and safety considerations for financial operations. The swap confirmation flow and error handling are particularly strong. However, the skill is verbose with some content that could be condensed (RPC provider comparisons, fee breakdowns) or split into reference files to improve token efficiency.
Suggestions
Move the detailed RPC provider options and private key import methods to a separate SETUP.md reference file, keeping only the default behavior in the main skill
Condense the referral fee section to 2-3 lines - the detailed breakdown is unnecessary for operational guidance
Remove the common token addresses table - Claude can look these up or they could be in a separate TOKENS.md reference
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity like emoji headers, explanatory tables for common knowledge (token addresses Claude could look up), and multiple RPC provider options that could be condensed. The referral fee explanation section is overly detailed for operational guidance. | 2 / 3 |
Actionability | Excellent executable code throughout with copy-paste ready bash commands, curl requests, and complete examples. Every operation has concrete, runnable commands with proper variable substitution and jq parsing. | 3 / 3 |
Workflow Clarity | The swap workflow is exemplary with clear 4-step sequence (quote → display/confirm → build → submit), explicit user confirmation checkpoints, retry logic with re-confirmation, and clear error handling table. Safety rules section reinforces validation requirements. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is monolithic at ~400 lines. Advanced topics like multiple RPC providers, private key import methods, and detailed fee breakdowns could be split into separate reference files. The structure is good but could benefit from linking to external docs. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
45f9fac
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.