fiat
Query Binance fiat payment capabilities — supported countries, currencies, payment methods, limits, and crypto prices — via public APIs, plus authenticated order/payment history lookup. Use whenever users ask about buying or selling crypto with fiat, depositing or withdrawing fiat, fiat-crypto exchange rates, payment options in a specific country, or their fiat order history — even if they don't explicitly mention Binance APIs.
68
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly articulates specific capabilities, provides comprehensive trigger terms covering natural user language, and explicitly addresses both what the skill does and when it should be used. The description is well-scoped to a distinct niche (Binance fiat payment APIs) and includes the helpful note about triggering even without explicit API mentions.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: querying supported countries, currencies, payment methods, limits, crypto prices via public APIs, and authenticated order/payment history lookup. Very detailed and actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (query Binance fiat payment capabilities including countries, currencies, methods, limits, prices, and order history) and 'when' (explicit 'Use whenever users ask about...' clause with multiple trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'buying or selling crypto with fiat', 'depositing or withdrawing fiat', 'fiat-crypto exchange rates', 'payment options in a specific country', 'fiat order history'. The note about 'even if they don't explicitly mention Binance APIs' is a helpful disambiguation cue. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific niche (Binance fiat payment APIs) with clear domain-specific triggers like 'fiat-crypto exchange rates', 'payment options in a specific country', and 'fiat order history'. Unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 is a solid, actionable skill with fully executable curl commands and well-structured API documentation. Its main weaknesses are moderate verbosity (locale lists, extensive action link guidance, and wallet method handling could be offloaded to reference files) and a workflow section that lacks explicit error handling and validation checkpoints for edge cases like suspended methods or empty results mid-workflow.
Suggestions
Move the locale list, language mapping table, and wallet payment method handling into a separate reference file to reduce the main skill's token footprint.
Add explicit validation/error-handling steps to the workflow — e.g., what to do when get_capabilities returns no supported business types, or when all payment methods are suspended.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with concrete API endpoints and response schemas, but includes some unnecessary verbosity — the locale list, language mapping table, and the wallet payment method section add bulk that could be trimmed or moved to a reference file. The action links section is quite lengthy for what it conveys. | 2 / 3 |
Actionability | Every API endpoint has a fully executable curl command with clear parameter specifications, response field paths, and concrete URL templates with examples. The country inference rules and price sorting logic are specific and copy-paste ready. | 3 / 3 |
Workflow Clarity | The recommended workflow provides a clear 3-step sequence and a shortcut for simple queries, which is good. However, there are no explicit validation checkpoints or error recovery steps beyond checking the response code — no guidance on what to do when get_capabilities returns unexpected results or when payment methods are all suspended. | 2 / 3 |
Progressive Disclosure | The skill references `references/sapi-endpoints.md` for authenticated endpoints, which is good progressive disclosure. However, the main file is quite long (~150+ lines) with the locale list, action link templates, wallet method logic, and country inference rules all inline — these could be split into reference files. No bundle files were provided to verify the referenced path exists. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- binance/binance-skills-hub
- Commit
68fcfa1
- 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.