moonpay
MoonPay fiat-to-crypto on-ramp integration. Buy and sell crypto with credit cards, bank transfers, and mobile payments.
69
Quality
59%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xterrybit/moonpay/SKILL.mdQuality
Discovery
40%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 identifies a clear, specific domain (MoonPay integration) with good distinctiveness, but lacks explicit trigger guidance and comprehensive capability listing. The absence of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill from a large skill library.
Suggestions
Add a 'Use when...' clause with trigger terms like 'MoonPay', 'buy crypto', 'sell crypto', 'fiat on-ramp', 'crypto payment gateway', or 'cryptocurrency purchase'
Expand specific capabilities to include integration actions like 'embed payment widget', 'handle transaction callbacks', 'verify KYC status', or 'process refunds'
Include common user phrasings like 'accept crypto payments', 'convert fiat to crypto', or 'cryptocurrency checkout'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (MoonPay fiat-to-crypto on-ramp) and lists some actions (buy and sell crypto) with payment methods, but doesn't comprehensively list specific integration capabilities like API endpoints, widget embedding, or transaction handling. | 2 / 3 |
Completeness | Describes what the skill does (MoonPay integration for buying/selling crypto) 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 terms like 'MoonPay', 'crypto', 'credit cards', 'bank transfers', 'mobile payments', but missing common variations users might say like 'purchase cryptocurrency', 'on-ramp', 'fiat gateway', or 'payment integration'. | 2 / 3 |
Distinctiveness Conflict Risk | MoonPay is a specific named service, making this clearly distinguishable from generic crypto or payment skills. The combination of 'MoonPay' + 'fiat-to-crypto' + 'on-ramp' creates a distinct niche unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 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-crafted API reference skill with excellent conciseness and actionability. The executable curl examples with proper authentication and jq filtering are immediately usable. However, it reads more as a reference card than a workflow guide - it would benefit from explicit integration sequences showing the typical buy flow with validation checkpoints.
Suggestions
Add a 'Typical Integration Flow' section showing the sequence: 1) Get quote → 2) Generate widget URL → 3) Handle webhook → 4) Verify transaction status, with explicit validation at each step
Include error handling guidance showing what to do when transactions fail or webhooks don't arrive
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient with no unnecessary explanations. Tables, code blocks, and bullet points convey information densely without explaining what MoonPay is or how APIs work. | 3 / 3 |
Actionability | Provides fully executable curl commands with proper variable substitution, jq filtering, and signature generation. Code is copy-paste ready with clear placeholders for user-specific values. | 3 / 3 |
Workflow Clarity | Individual operations are clear, but the overall integration workflow lacks explicit sequencing. No validation checkpoints between steps like 'get quote -> create transaction -> verify status' or error recovery guidance. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in one file. Reference tables (currencies, payment methods) could be split out, and external links are provided but no internal file references for advanced topics. | 2 / 3 |
Total | 10 / 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.
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
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.