CtrlK
BlogDocsLog inGet started
Tessl Logo

alchemy-pay

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

51

Quality

57%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/0xterrybit/alchemy-pay/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

64%

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 API integration skill with excellent actionability — the bash examples with signature generation are particularly well done and immediately usable. However, it lacks workflow sequencing and validation checkpoints (e.g., verifying webhook signatures, handling errors), and some content like payment method tables and crypto lists add bulk without proportional value. The NFT checkout and off-ramp features are listed but never actually documented with examples.

Suggestions

Add an explicit numbered workflow showing the typical integration sequence (check supported assets → get rate → create order → handle webhook → verify signature) with validation at each step

Include a concrete webhook signature verification example, since it's listed as a safety rule but has no implementation code

Remove or move the supported payment methods and supported cryptocurrencies tables to a separate reference file — these are reference data that changes and doesn't need to be in the main skill

Add examples for off-ramp and NFT checkout endpoints, or remove them from the features list if they're not being documented

DimensionReasoningScore

Conciseness

Generally efficient with good use of tables and code blocks, but includes some unnecessary elements like emoji decorations, the supported payment methods/cryptocurrencies tables (reference material Claude doesn't need memorized), and the features bullet list which largely restates the description. The supported crypto list and payment methods could be omitted or linked externally.

2 / 3

Actionability

Provides fully executable bash commands with proper signature generation, curl requests, and environment variable handling. The on-ramp order creation example is copy-paste ready with clear placeholders, and the widget integration HTML is concrete and usable.

3 / 3

Workflow Clarity

The API calls are clearly shown but there's no explicit workflow sequence (e.g., 'first check supported cryptos, then get rate, then create order, then verify via webhook'). Missing validation steps — no guidance on verifying the response status codes, checking webhook signatures (mentioned in safety rules but no implementation), or handling error recovery from failed orders.

2 / 3

Progressive Disclosure

Content is reasonably organized with clear sections and tables, but it's a monolithic file with no bundle files. The supported payment methods, error codes, and cryptocurrency lists could be split into reference files. External links are provided but no internal file references exist for deeper topics like webhook signature verification or NFT checkout (mentioned as a feature but never detailed).

2 / 3

Total

9

/

12

Passed

Description

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 does a good job listing specific capabilities and naming the product clearly, making it distinctive. However, it critically lacks any 'Use when...' guidance, which would help Claude know when to select this skill from a large pool. Adding explicit trigger conditions and a few more natural user-facing keywords would significantly improve it.

Suggestions

Add a 'Use when...' clause such as 'Use when the user asks about Alchemy Pay integration, fiat-to-crypto payments, crypto on-ramp/off-ramp, or NFT checkout with ACH.'

Include natural user-facing trigger terms like 'buy crypto with credit card', 'convert fiat to crypto', 'crypto cash out', or 'accept crypto payments' to improve keyword coverage.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'fiat-to-crypto payment gateway integration', 'on-ramp', 'off-ramp', 'merchant payments', and 'NFT checkout services'. These are distinct, concrete 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. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent (not even implied well), this scores a 1.

1 / 3

Trigger Term Quality

Includes relevant keywords like 'ACH', 'fiat-to-crypto', 'on-ramp', 'off-ramp', 'merchant payments', 'NFT checkout', and 'payment gateway'. However, it misses common user variations like 'buy crypto with credit card', 'cash out crypto', 'fiat payment', or 'Alchemy Pay SDK'.

2 / 3

Distinctiveness Conflict Risk

Very clearly scoped to Alchemy Pay (ACH) specifically, with distinct triggers like 'fiat-to-crypto', 'on-ramp/off-ramp', and 'NFT checkout'. Unlikely to conflict with other payment or crypto skills due to the named product specificity.

3 / 3

Total

9

/

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.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.