solana-pay

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

Quality

63%

Does it follow best practices?

Impact

Pending

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

50%

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 effectively communicates specific capabilities for Solana Pay integration with concrete actions. However, it critically lacks explicit trigger guidance ('Use when...'), which limits Claude's ability to know when to select this skill. The domain is distinctive but could benefit from broader payment-related trigger terms.

Suggestions

Add a 'Use when...' clause with trigger scenarios like 'Use when the user asks about Solana payments, crypto payment integration, or generating payment QR codes for SOL transactions'

Include additional natural trigger terms users might say: 'crypto payments', 'SOL payments', 'blockchain payments', 'payment links'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Generate payment requests, QR codes, and verify transactions' - these are clear, actionable capabilities.	3 / 3
Completeness	Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Solana Pay', 'payment requests', 'QR codes', 'transactions', 'Solana blockchain', but missing common variations users might say like 'crypto payments', 'SOL payments', or 'blockchain payments'.	2 / 3
Distinctiveness Conflict Risk	Very clear niche with 'Solana Pay protocol' and 'Solana blockchain' - unlikely to conflict with other skills due to specific blockchain/protocol focus.	3 / 3
	Total	9 / 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 solid, actionable skill with excellent executable code examples and clear workflows for payment generation and verification. The main weaknesses are some unnecessary marketing-style content and a monolithic structure that could benefit from splitting advanced topics into separate files. The safety rules and error handling sections are well done.

Suggestions

Remove the marketing-style feature bullets and fee comparison table - Claude doesn't need convincing about Solana Pay's benefits

Consider moving the POS integration scripts and Transaction Request Server example to separate referenced files to improve progressive disclosure

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary content like the fee comparison table and feature bullet points with marketing-style descriptions (💸 Instant Payments, 🆓 Near-Zero Fees) that Claude doesn't need. The core technical content is efficient, but there's padding.	2 / 3
Actionability	Excellent executable examples throughout - complete bash scripts for generating payment URLs, QR codes, verifying transactions, and polling for payments. The JavaScript server example is also complete and copy-paste ready.	3 / 3
Workflow Clarity	Clear multi-step workflows with explicit validation: generate payment → save reference → poll for confirmation → verify transaction details. The safety rules section explicitly requires verification before fulfilling orders, and error handling provides clear recovery paths.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but it's somewhat monolithic. The POS integration scripts and transaction request server example could be split into separate files. Links to external docs are provided but internal progressive disclosure is limited.	2 / 3
	Total	10 / 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: 45f9fac

Reviewed: 27 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.