CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

solana

Query Solana wallets, tokens, txs, and NFTs in USD.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/blockchain/solana/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-organized, highly actionable CLI reference: every command is executable with real examples, setup/verification checkpoints are explicit, and pitfalls candidly document rate limits and heuristic limitations. The main weakness is token efficiency — the absolute script path and environment facts are repeated many times — and the script reference uses an install path instead of a bundle-relative one.

Suggestions

State the script path once (e.g. "Script: scripts/solana_client.py (run as python scripts/solana_client.py ...)") and use a short form in the per-command examples instead of repeating the full ~/.hermes/... path ten times.

Deduplicate the stdlib/no-API-key and rate-limit details between the intro, Prerequisites, and Pitfalls sections — mention each fact once.

Reference the script by its bundle-relative path (scripts/solana_client.py) so the reference matches the actual bundle structure.

DimensionReasoningScore

Conciseness

The body is operational with no padding about what Solana/blockchain is, but it repeats itself: the full absolute script path "~/.hermes/skills/blockchain/solana/scripts/solana_client.py" is spelled out ~10 times, and the stdlib/no-API-key and rate-limit facts each appear in both the intro/Prerequisites and Pitfalls sections. This matches anchor 3 ('mostly efficient but could be tightened') rather than anchor 4, since the repetition is systematic, not minor.

3 / 5

Actionability

Every command is copy-paste ready with real example addresses and mints (e.g. wallet 9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM, BONK mint DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263), documented flags (--limit, --all, --no-prices, --min-sol), and stated expected outputs. The Quick Reference block covers the full command surface, matching anchor 5's 'fully executable, copy-paste ready, specific examples covering common cases'.

5 / 5

Workflow Clarity

The skill is a set of single read-only commands, each unambiguous, with an explicit "Setup Check" (connectivity confirmation via stats), a "When to Use" section mapping user intents to commands, a Verification section stating expected output, and error-recovery guidance in Pitfalls (429 retry with exponential backoff, --no-prices fallback). No destructive or batch operations, so no cap applies; this matches anchor 5's explicit validation and feedback-loop criteria.

5 / 5

Progressive Disclosure

Structure is good: a lean overview plus clearly headed sections (When to Use, Quick Reference, Procedure, Pitfalls, Verification) and a single one-level-deep bundle reference to scripts/solana_client.py, which exists and implements all 8 documented commands. It falls short of anchor 5 because the script is referenced via an absolute install path (~/.hermes/skills/...) rather than a bundle-relative path (scripts/solana_client.py), slightly obscuring the reference against the actual bundle layout.

4 / 5

Total

17

/

20

Passed

Description

53%Weight 40%Scale 1-5

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 is concise and names a specific domain with concrete object types, but it is purely a 'what' statement: it lacks any 'when to use' trigger guidance and under-represents the skill's actual command surface (whales, stats, price). Adding an explicit use-when clause with natural user phrases would raise completeness and trigger quality substantially.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks about a Solana wallet balance, token price, transaction, NFT holdings, or network stats."

Include the remaining capabilities (whale/large-transfer detection, network stats/TPS, price lookup) so the description covers the full command surface.

Add natural synonyms users actually say — "balance", "portfolio value", "price", "transactions" — to improve trigger-term coverage.

DimensionReasoningScore

Specificity

"Query Solana wallets, tokens, txs, and NFTs in USD" names the domain and one concrete action applied to specific object types, but relies on a single generic verb and omits capabilities the skill actually has (whale detection, network stats, price lookup). It matches anchor 3 (domain + concrete actions, not comprehensive) better than anchor 4, whose example lists several distinct action verbs.

3 / 5

Completeness

The 'what' is clear (query wallets, tokens, txs, NFTs with USD pricing), but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is concrete and multi-part, not vague.

3 / 5

Trigger Term Quality

Relevant keywords are present ("Solana", "wallets", "tokens", "txs", "NFTs", "USD") but common natural phrases users would say are missing: "price", "balance", "portfolio", "transactions", "blockchain". This sits at anchor 3 (some relevant keywords, missing common variations) rather than anchor 4's 'good keyword coverage with only a few natural terms missing'.

3 / 5

Distinctiveness Conflict Risk

"Solana" pins a clear niche, so the description is mostly distinct with minimal conflict risk against non-Solana skills. It falls short of anchor 5 because queries like "token price in USD" or "wallet balance" could also match generic crypto-pricing or other blockchain skills since no Solana-explicit trigger phrasing is given.

4 / 5

Total

13

/

20

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 — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/blockchain/solana/SKILL.md

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.