bybit-futures

Bybit Futures trading with DB tracking

Quality

55%

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 ./src/skills/bundled/bybit-futures/SKILL.md

Quality

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 a platform and general domain but fails to specify concrete capabilities or provide any guidance on when to use the skill. The absence of a 'Use when...' clause and specific actions makes it difficult for Claude to confidently select this skill from a larger pool.

Suggestions

Add specific concrete actions like 'Place futures orders, monitor open positions, track P&L, query trade history'

Include a 'Use when...' clause with trigger terms like 'Bybit', 'futures', 'crypto trading', 'perpetual contracts', 'leverage', 'positions'

Clarify what 'DB tracking' means - e.g., 'Logs all trades to a local database for performance analysis and reporting'

Dimension	Reasoning	Score
Specificity	The description only names a domain ('Bybit 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 tracking) but completely lacks any 'when' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Contains some relevant keywords ('Bybit', 'Futures', 'trading', 'DB') that users might say, but misses common variations like 'crypto', 'derivatives', 'positions', 'orders', or 'database'.	2 / 3
Distinctiveness Conflict Risk	'Bybit' is a specific platform which helps distinguish it, but 'Futures trading' and 'DB tracking' are generic enough to potentially overlap with other trading or database 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 tables and examples provide clear, executable guidance. The main weakness is the lack of validation/verification workflows for trading operations - users should know how to confirm orders executed correctly and handle errors in financial transactions.

Suggestions

Add a brief workflow section showing how to verify order execution (e.g., '/bb long BTCUSDT 0.01 10x' then '/bb positions' to confirm)

Include guidance on error handling or what to do if a command fails, especially for financial operations

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient - no unnecessary explanations of what futures trading is or how APIs work. Every line serves a purpose with zero padding.	3 / 3
Actionability	Fully concrete with copy-paste ready commands, clear syntax patterns, and practical examples. The command tables provide exact syntax with parameters clearly indicated.	3 / 3
Workflow Clarity	Commands are clearly documented but there's no validation workflow for trading operations. Missing guidance on verifying order execution, checking position status after opening, or handling failed orders - important for financial operations.	2 / 3
Progressive Disclosure	Well-organized with clear sections progressing from quick start to detailed commands to examples. For a command reference skill of this size, the structure is appropriate without needing external file references.	3 / 3
	Total	11 / 12 Passed

Validation

90%

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 — 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: 29 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.