binance-futures
Binance Futures trading with DB tracking
68
55%
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 ./src/skills/bundled/binance-futures/SKILL.mdQuality
Discovery
22%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 description is too terse and lacks the detail needed for effective skill selection. It names the domain but fails to specify concrete actions or provide any guidance on when to use the skill. The 'DB tracking' component is unclear and adds little value without explanation.
Suggestions
Add specific actions like 'Place futures orders, monitor open positions, query trade history, calculate PnL'
Add a 'Use when...' clause with trigger terms like 'Binance', 'futures trading', 'crypto positions', 'leverage orders', 'perpetual contracts'
Clarify what 'DB tracking' means - e.g., 'Logs all trades to a local database for performance analysis'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names a domain ('Binance Futures trading') and mentions 'DB tracking' but provides no concrete actions like placing orders, monitoring positions, or querying trade history. | 1 / 3 |
Completeness | The description weakly addresses 'what' (trading with DB tracking) but completely lacks any 'when' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | 'Binance Futures' and 'trading' are relevant keywords users might say, but missing common variations like 'crypto trading', 'futures orders', 'positions', 'leverage', or 'perpetual contracts'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Binance Futures' is fairly specific and distinguishes from general trading skills, but 'DB tracking' is vague and could overlap with database or analytics skills. | 2 / 3 |
Total | 6 / 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 command reference skill that excels at conciseness and actionability. The command tables and examples are immediately usable. However, for a trading skill involving real money and leverage up to 125x, the lack of validation steps (confirming order fills, checking position state, handling errors) is a notable gap.
Suggestions
Add a validation workflow section showing how to verify order execution (e.g., 'After /bf long, run /bf positions to confirm entry')
Include error handling guidance for common failure scenarios (insufficient margin, invalid symbol, network issues)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what futures trading is or how Binance works. Every line provides actionable command syntax or essential setup information. | 3 / 3 |
Actionability | Fully concrete with copy-paste ready commands. Clear syntax patterns with parameters shown (e.g., `<symbol> <size> [leverage]x`), and practical examples demonstrating real usage scenarios. | 3 / 3 |
Workflow Clarity | Commands are clearly listed but lacks validation checkpoints for risky trading operations. No guidance on verifying order execution, checking position state after trades, or error recovery for failed orders. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (Quick Start, Commands by category, Examples). For a command reference skill of this size, the structure is appropriate with logical groupings and no need for external file references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- alsk1992/CloddsBot
- Commit
2a8c94e
- 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.