bybit-futures
Bybit Futures trading with DB tracking
60
51%
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/bybit-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 extremely terse and lacks both concrete action details and explicit trigger guidance. While 'Bybit Futures' provides some domain specificity, the description fails to explain what the skill actually does or when Claude should select it. It reads more like a title than a functional description.
Suggestions
Add specific concrete actions such as 'Places and manages futures orders on Bybit, tracks positions, calculates PnL, and logs trade history to a database.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Bybit futures trading, placing leveraged orders, tracking crypto derivatives positions, or querying trade history from the database.'
Replace 'DB tracking' with more descriptive language like 'stores trade history and position data in a local database' to reduce ambiguity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Bybit Futures trading') and mentions 'DB tracking' but does not list any concrete actions like placing orders, monitoring positions, calculating PnL, or querying trade history. | 1 / 3 |
Completeness | The description weakly addresses 'what' (Bybit Futures trading with DB tracking) and completely omits 'when' — there is no 'Use when...' clause or any explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | 'Bybit', 'Futures', and 'trading' are natural keywords a user might say, but the description lacks common variations like 'perpetual contracts', 'leverage', 'positions', 'orders', or 'crypto derivatives'. 'DB tracking' is vague jargon. | 2 / 3 |
Distinctiveness Conflict Risk | 'Bybit Futures' is fairly specific and unlikely to conflict with generic trading or database skills, but 'DB tracking' is vague enough to overlap with other database-related skills. The niche is somewhat clear but not sharply defined. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a clean, well-structured command reference that excels at conciseness and actionability. The table-based organization makes commands easy to discover and the examples are practical. The main weakness is the lack of validation/verification guidance for financial operations—there's no mention of confirming order fills, checking position status after opening, or handling errors, which is important for leveraged trading.
Suggestions
Add a brief workflow section showing verification after trading actions (e.g., after `/bb long`, check `/bb positions` to confirm fill, verify entry price)
Include error handling guidance or common failure scenarios (e.g., insufficient margin, invalid symbol, API rate limits)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every token earns its place. No unnecessary explanations of what Bybit is, what futures are, or how leverage works. The content is pure reference material organized in tables and examples. | 3 / 3 |
Actionability | Commands are fully concrete and copy-paste ready with specific syntax patterns. The examples section provides real-world usage with inline comments explaining each command's purpose. | 3 / 3 |
Workflow Clarity | The quick start shows a basic sequence (credentials → balance → trade → stats), but there are no validation checkpoints or feedback loops for trading operations. For destructive financial operations like leveraged trading, missing confirmation/verification steps (e.g., verify position opened, check fill price) is a notable gap. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but everything is inline in one file. The database tracking aspect mentioned in the description could warrant a separate reference file. However, the skill is relatively concise so this is a minor issue. | 2 / 3 |
Total | 10 / 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
e71a5f6
- 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.