binance-pay

Binance Pay integration for crypto payments. Send, receive, and accept cryptocurrency payments with the world's largest exchange.

Quality

60%

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/binance-pay/SKILL.md

Quality

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 provides a basic understanding of the skill's purpose but lacks the explicit trigger guidance required for Claude to reliably select it from a large skill library. The capabilities are stated at a high level without sufficient detail, and the absence of a 'Use when...' clause significantly limits its effectiveness for skill selection.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'Binance Pay', 'crypto payment', 'send Bitcoin', 'accept cryptocurrency', or 'exchange payment'

Expand specific capabilities beyond send/receive/accept - include details like 'generate payment links', 'check transaction status', 'list supported cryptocurrencies', or 'process merchant payments'

Add common user phrases and variations such as 'pay with crypto', 'BTC payment', 'digital currency transfer' to improve trigger term coverage

Dimension	Reasoning	Score
Specificity	Names the domain (Binance Pay, crypto payments) and lists some actions (send, receive, accept), but lacks comprehensive detail about specific capabilities like transaction types, supported currencies, or API operations.	2 / 3
Completeness	Describes what it does (send/receive/accept crypto payments) 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 'Binance Pay', 'crypto payments', 'cryptocurrency', 'send', 'receive', but misses common variations users might say like 'Bitcoin payment', 'crypto transfer', 'digital currency', or specific coin names.	2 / 3
Distinctiveness Conflict Risk	The 'Binance Pay' specificity helps distinguish it from generic payment skills, but 'crypto payments' could overlap with other cryptocurrency or payment processing skills without clearer boundaries.	2 / 3
	Total	7 / 12 Passed

Implementation

87%

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 integration skill with excellent actionability through complete, executable curl examples and efficient token usage. The main weakness is the lack of explicit workflow guidance showing how operations connect (e.g., create -> poll status -> handle webhook) and missing error handling patterns for common failure scenarios.

Suggestions

Add a 'Typical Payment Flow' section showing the sequence: create order -> redirect user -> receive webhook -> verify -> fulfill, with validation checkpoints

Include error response examples and handling guidance for common failures (invalid signature, expired order, insufficient balance)

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, presenting only essential information without explaining what Binance or crypto payments are. Every section serves a purpose with no unnecessary padding.	3 / 3
Actionability	Provides fully executable bash/curl commands with complete authentication setup, signature generation, and all required headers. Code is copy-paste ready with clear placeholders for user-specific values.	3 / 3
Workflow Clarity	While individual operations are clear, there's no explicit workflow sequence for common tasks like 'create order -> verify payment -> fulfill'. Missing validation checkpoints between steps and no error handling guidance for failed API calls.	2 / 3
Progressive Disclosure	Well-organized with clear sections progressing from setup to operations to reference tables. External links to official docs are provided for deeper information without nesting references.	3 / 3
	Total	11 / 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.