solana-pay

Solana Pay protocol integration. Generate payment requests, QR codes, and verify transactions on Solana blockchain.

Quality

66%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/0xterrybit/solana-pay/SKILL.md

Quality

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.

The description is concise and specific about its capabilities within the Solana Pay domain, listing concrete actions like generating payment requests, QR codes, and verifying transactions. Its main weakness is the absence of an explicit 'Use when...' clause that would help Claude know exactly when to select this skill. The trigger terms are decent but could include more natural user language variations.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user asks about Solana payments, crypto payment integration, or generating payment links on Solana.'

Include additional natural trigger terms users might say, such as 'crypto payments', 'SOL transfers', 'wallet payments', 'checkout with Solana', or 'SPL tokens'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Generate payment requests', 'QR codes', and 'verify transactions on Solana blockchain'. These are clear, actionable capabilities.	3 / 3
Completeness	Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Includes good keywords like 'Solana Pay', 'payment requests', 'QR codes', 'transactions', 'Solana blockchain', but misses common user variations like 'crypto payments', 'SOL', 'wallet', or 'checkout'.	2 / 3
Distinctiveness Conflict Risk	Very distinct niche — 'Solana Pay protocol integration' is highly specific and unlikely to conflict with other skills. The combination of Solana blockchain + payment protocol + QR codes creates a clear, unique identity.	3 / 3
	Total	10 / 12 Passed

Implementation

64%

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

The skill provides strong actionable content with executable bash scripts and real-world examples for Solana Pay integration. However, it suffers from some unnecessary marketing content (fee comparisons, feature bullets), lacks a clear end-to-end workflow with explicit validation checkpoints between payment generation and fulfillment, and could benefit from splitting detailed scripts into separate bundle files.

Suggestions

Remove the fee comparison table and feature bullet points (wallet support, finality times) — these are marketing content that doesn't help Claude execute tasks.

Add an explicit end-to-end workflow section: 1. Generate payment URL with unique reference → 2. Display QR → 3. Poll for transaction → 4. **Validate** recipient matches merchant wallet → 5. **Validate** amount matches expected → 6. Only then fulfill order → 7. If validation fails, reject and alert.

Split the POS scripts (pos_payment.sh, wait_payment.sh) and the transaction request server example into separate bundle files, referencing them from the main SKILL.md.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary content like the fee comparison table (marketing fluff, not actionable), wallet support bullet points, and feature descriptions that don't help Claude execute tasks. The core code examples are reasonably lean, but the overall document could be tightened significantly.	2 / 3
Actionability	The skill provides fully executable bash scripts and code examples for generating payment URLs, QR codes, verifying transactions, and polling for payments. Commands are copy-paste ready with concrete variable assignments and real token addresses.	3 / 3
Workflow Clarity	The POS integration shows a generate-then-poll workflow, and safety rules mention verification steps, but the verification workflow lacks explicit sequencing with validation checkpoints. There's no clear 'generate → display → poll → validate recipient + amount → fulfill' end-to-end workflow with feedback loops for error recovery.	2 / 3
Progressive Disclosure	The content is a long monolithic document (~200 lines) with no references to supporting files. The POS scripts, transaction request server example, and token address table could be split into separate files. However, sections are well-organized with clear headers.	2 / 3
	Total	9 / 12 Passed

Validation

81%

Warnings & errors only

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

Repository: Demerzels-lab/elsamultiskillagent
Commit: f45fcb5

Reviewed: 23 days ago

Table of Contents

Discovery Implementation Validation

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.