trading-signal
Subscribe and retrieve on-chain Smart Money signals. Monitor trading activities of smart money addresses, including buy/sell signals, trigger price, current price, max gain, and exit rate. Use this skill when users are looking for investment opportunities — smart money signals can serve as valuable references for potential trades.
64
75%
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 ./skills/binance-web3/trading-signal/SKILL.mdQuality
Discovery
85%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 a strong description that clearly defines what the skill does (subscribe/retrieve smart money signals with specific data points) and when to use it (investment opportunities). The main weakness is that trigger term coverage could be broader to capture more natural user phrasings related to crypto/on-chain analytics.
Suggestions
Add more natural trigger terms users might say, such as 'whale tracking', 'whale wallets', 'on-chain analytics', 'crypto signals', or 'token alerts' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: subscribe, retrieve on-chain Smart Money signals, monitor trading activities. Also specifies concrete data points: buy/sell signals, trigger price, current price, max gain, and exit rate. | 3 / 3 |
Completeness | Clearly answers both what ('Subscribe and retrieve on-chain Smart Money signals, monitor trading activities...') and when ('Use this skill when users are looking for investment opportunities — smart money signals can serve as valuable references for potential trades'). | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'smart money signals', 'buy/sell signals', 'trading activities', and 'investment opportunities', but misses common user variations like 'whale tracking', 'whale wallets', 'on-chain analytics', 'token alerts', or 'crypto signals'. | 2 / 3 |
Distinctiveness Conflict Risk | The description targets a very specific niche — on-chain smart money signal monitoring with specific metrics like trigger price, max gain, and exit rate. This is unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 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 API reference skill with excellent actionability — complete curl examples, detailed request/response schemas, and clear parameter documentation. Its main weaknesses are moderate verbosity (duplicate examples, unnecessary 'Use Cases' section), lack of error handling guidance, and a monolithic structure that would benefit from splitting the detailed field reference tables into a separate file.
Suggestions
Remove the duplicate curl examples (keep either the one in the API section or the 'Example Requests' section, not both) and drop the 'Use Cases' section which describes things Claude can infer.
Add error handling guidance: what does a non-'000000' code look like, and how should Claude respond to API failures or empty results?
Move the detailed response field tables into a separate REFERENCE.md file and link to it from the main skill, keeping only the most essential fields inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly detailed and well-structured as an API reference, but contains some redundancy — the example request appears twice (once in the API section and again in 'Example Requests'), and the 'Use Cases' section describes things Claude can infer. The response field tables are thorough but could be more compact. | 2 / 3 |
Actionability | Provides fully executable curl commands, complete request/response examples with real JSON structures, specific headers, and detailed parameter tables. Claude can directly copy and execute these API calls. | 3 / 3 |
Workflow Clarity | This is essentially a single API call skill, so the workflow is straightforward. However, there's no guidance on error handling (what if code != '000000'?), no validation steps for responses, and no clear sequence for how to interpret and act on the signals retrieved. | 2 / 3 |
Progressive Disclosure | The content is organized with clear section headers and tables, but it's a long monolithic document (~200 lines) with detailed response field tables that could be split into a reference file. No bundle files are provided despite the length warranting separation of the API reference details. | 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.