alchemy-pay

Alchemy Pay (ACH) fiat-to-crypto payment gateway integration. On-ramp, off-ramp, merchant payments, and NFT checkout services.

Quality

64%

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/alchemy-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 identifies a specific service (Alchemy Pay) and lists concrete capabilities, making it distinctive and specific. However, it completely lacks trigger guidance ('Use when...'), which is critical for Claude to know when to select this skill. The trigger terms could also be expanded to include more natural user language.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when integrating crypto payments, setting up fiat-to-crypto conversion, or implementing NFT purchase flows'

Include natural user terms like 'buy crypto', 'sell crypto', 'crypto payment integration', 'accept cryptocurrency payments'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'On-ramp, off-ramp, merchant payments, and NFT checkout services' - these are distinct, actionable capabilities within the fiat-to-crypto domain.	3 / 3
Completeness	Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all.	1 / 3
Trigger Term Quality	Includes relevant terms like 'fiat-to-crypto', 'on-ramp', 'off-ramp', 'NFT checkout', but missing common user variations like 'buy crypto', 'sell crypto', 'crypto payments', 'ACH payments', or 'payment processing'.	2 / 3
Distinctiveness Conflict Risk	Very specific niche: 'Alchemy Pay (ACH)' is a named service, and 'fiat-to-crypto payment gateway' is a distinct domain unlikely to conflict with general payment or crypto skills.	3 / 3
	Total	9 / 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 API integration skill with excellent actionability - the bash examples are complete and executable with proper authentication. The content is concise and respects Claude's intelligence. However, it lacks explicit multi-step workflows showing how to handle the full payment lifecycle (create -> verify -> handle callbacks) and could benefit from splitting reference material into separate files.

Suggestions

Add an explicit workflow section showing the complete payment flow: create order -> verify response -> poll status or await webhook -> handle completion/failure

Include webhook signature verification code example to match the safety rule about verifying signatures

Consider moving reference tables (payment methods, cryptocurrencies, error codes) to a separate REFERENCE.md file

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient, using tables for structured data, minimal prose, and no unnecessary explanations of concepts Claude would already know. Every section serves a clear purpose.	3 / 3
Actionability	Provides fully executable bash commands with proper authentication setup, signature generation, and curl examples that are copy-paste ready. The widget integration HTML is also directly usable.	3 / 3
Workflow Clarity	While individual API calls are clear, there's no explicit workflow for common multi-step processes (e.g., create order -> poll status -> handle webhook). Missing validation checkpoints for verifying order creation success before proceeding.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections, but everything is in one file. The supported cryptocurrencies, payment methods, and error codes could be split into reference files, with SKILL.md providing a quick start and linking out.	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.