binance-pay
Binance Pay integration for crypto payments. Send, receive, and accept cryptocurrency payments with the world's largest exchange.
45
48%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xterrybit/binance-pay/SKILL.mdQuality
Discovery
32%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 the domain (Binance Pay) and basic actions (send, receive, accept payments) but lacks depth in specific capabilities and completely omits explicit trigger guidance ('Use when...'). The marketing-style phrase 'world's largest exchange' adds no functional value for skill selection. It needs more concrete actions and clear trigger conditions to help Claude reliably select this skill.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'Use when the user asks about Binance Pay, crypto payments, cryptocurrency transfers, merchant checkout, or payment orders via Binance.'
List more specific concrete actions such as 'create payment orders, generate QR codes, check transaction status, configure merchant callbacks, handle refunds'.
Replace the marketing phrase 'world's largest exchange' with additional natural trigger terms users might use, such as 'BTC payments', 'USDT transfers', or 'crypto payment gateway'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Binance Pay, crypto payments) and some actions (send, receive, accept cryptocurrency payments), but doesn't list specific concrete actions like creating payment orders, checking transaction status, managing merchant accounts, or handling webhooks. | 2 / 3 |
Completeness | Describes what it does (send, receive, accept crypto payments via Binance Pay) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' portion is also fairly thin, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Binance Pay', 'crypto payments', 'cryptocurrency payments', and 'send/receive', but misses common variations users might say such as 'Bitcoin payment', 'crypto checkout', 'digital currency transfer', 'BTC', 'USDT', or 'payment gateway'. | 2 / 3 |
Distinctiveness Conflict Risk | Mentioning 'Binance Pay' specifically helps distinguish it from generic payment or crypto skills, but 'crypto payments' and 'send, receive' are broad enough to potentially overlap with other cryptocurrency or payment integration skills. | 2 / 3 |
Total | 7 / 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.
This skill provides strong actionable content with executable curl commands and proper authentication setup for Binance Pay integration. However, it lacks a clear end-to-end workflow with validation checkpoints critical for financial operations, and the repeated curl patterns and reference tables make it longer than necessary. The content would benefit from a workflow-oriented structure and better separation of reference material.
Suggestions
Add an explicit end-to-end workflow section (e.g., 1. Create order → 2. Redirect user → 3. Receive webhook → 4. Verify signature → 5. Check order status → 6. Fulfill order) with validation checkpoints at each step.
Extract the repeated curl pattern into a single template and show only the varying PAYLOAD and endpoint for each operation to reduce duplication.
Move reference tables (supported currencies, order status codes, webhook events) into a separate REFERENCE.md file and link to it from the main skill.
Remove marketing-style content like '200M+ Users - Access to Binance ecosystem' that provides no actionable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with concrete code examples, but includes some unnecessary elements like the emoji-laden features list ('200M+ Users - Access to Binance ecosystem' is marketing fluff), and the repeated curl command structure could be templated once rather than duplicated across four nearly identical sections. | 2 / 3 |
Actionability | The skill provides fully executable bash/curl commands for every operation, complete with authentication setup, signature generation, and proper headers. The code is copy-paste ready with clear placeholder markers for variable values. | 3 / 3 |
Workflow Clarity | The operations are clearly presented individually, but there's no explicit workflow sequence (e.g., create order → verify payment via webhook → fulfill → handle refund if needed). The safety rules mention checking order status before fulfilling but don't integrate this into a step-by-step workflow with validation checkpoints. For financial operations, missing feedback loops cap this at 2. | 2 / 3 |
Progressive Disclosure | The content is a single monolithic file with no bundle files to offload reference material. The supported currencies table, order status codes, and webhook events could be in separate reference files. External links are provided but the inline content is heavy for a SKILL.md overview. | 2 / 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.
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
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.