CtrlK
BlogDocsLog inGet started
Tessl Logo

bybit-futures

Bybit Futures trading with DB tracking

58

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/bybit-futures/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, actionable, and well-structured, but as a destructive/batch trading skill it lacks any validation or confirmation steps before risky operations like closeall or leveraged position opens, which caps workflow clarity.

Suggestions

Add an explicit confirmation/validation checkpoint before destructive batch operations such as '/bb closeall' (e.g. list open positions and require confirmation before closing all).

Add a pre-trade validation step for leveraged orders (e.g. check current price, position size, and margin before opening '/bb long <symbol> <size> <leverage>x').

Include a position-existence check before '/bb close <symbol>' and '/bb tp'/'/bb sl' so failures are caught explicitly.

DimensionReasoningScore

Conciseness

The body is lean and efficient — only command tables and brief examples, with no padding or explanations of concepts Claude already knows, matching the 5-anchor 'Lean and efficient; assumes Claude's competence; every token earns its place'.

5 / 5

Actionability

Commands are concrete and executable with real syntax and arguments (e.g. '/bb long BTCUSDT 0.01 10x'), and the Examples section provides copy-paste-ready invocations covering common cases, matching the 5-anchor.

5 / 5

Workflow Clarity

This is a destructive/batch skill (closeall, 100x leverage, closing positions) with no validation or confirmation checkpoints, and the judging guideline caps workflow clarity at 3 for such skills missing validation steps.

3 / 5

Progressive Disclosure

It is a simple, single-purpose skill with well-organized sections (Quick Start, Commands by category, Examples) and no need for external references, qualifying for the under-50-lines/no-external-references exception at score 5.

5 / 5

Total

18

/

20

Passed

Description

48%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is short and tied to a distinct niche, but it lacks concrete action verbs, trigger synonyms, and any 'Use when...' guidance, which caps completeness and limits specificity.

Suggestions

Add concrete actions: e.g. 'Open and close leveraged perpetual positions, set take-profit/stop-loss, and log trades to a database.'

Add a 'Use when...' clause with trigger terms: e.g. 'Use when the user wants to trade Bybit perpetual futures, check positions, or review trading history.'

Include synonyms/extensions like 'perp', 'perpetuals', 'leverage', and 'crypto derivatives' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('Bybit Futures') and two actions ('trading', 'DB tracking'), but the actions are minimal and generic rather than concrete (no 'open positions', 'set leverage', 'log trades'). It fits the score-2 anchor 'Names the domain but actions are minimal or generic' better than the 3-anchor, which expects at least 1-2 concrete named actions.

2 / 5

Completeness

There is a clear 'what' (trading with DB tracking) but no 'when'/'Use when...' clause at all, and the judging guideline caps completeness at 3 when explicit trigger guidance is missing.

3 / 5

Trigger Term Quality

'Bybit Futures' is a natural term a user would say, but there are no synonyms or variations ('perp', 'perpetuals', 'leverage', 'crypto derivatives'), matching the 3-anchor 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

Tied to a specific exchange (Bybit) and product (Futures), giving it a clear niche with only minor overlap risk against generic crypto/trading skills, matching the 4-anchor 'Mostly distinct; minor overlap risk'.

4 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
alsk1992/CloddsBot
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.