bybit

Bybit exchange integration. Trade spot, derivatives, and perpetuals with up to 100x leverage.

Quality

48%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/0xterrybit/bybit/SKILL.md

Quality

Discovery

40%

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 identifies a clear niche (Bybit exchange trading) and mentions some trading types, giving it reasonable distinctiveness. However, it lacks a 'Use when...' clause, misses common user trigger terms like 'crypto', 'futures', or 'order', and doesn't enumerate specific capabilities beyond general trading categories.

Suggestions

Add a 'Use when...' clause such as 'Use when the user asks about Bybit trading, placing crypto orders, checking Bybit positions, or managing leverage on Bybit.'

Include more natural trigger terms users would say, such as 'crypto trading', 'futures', 'margin trading', 'order placement', 'Bybit API', and 'portfolio/positions'.

List more specific concrete actions like 'place limit/market orders, check account balances, view open positions, retrieve market data, set stop-loss/take-profit'.

Dimension	Reasoning	Score
Specificity	Names the domain (Bybit exchange) and some actions (trade spot, derivatives, perpetuals, leverage), but doesn't list comprehensive specific actions like placing orders, checking balances, managing positions, or retrieving market data.	2 / 3
Completeness	Describes what it does (trade on Bybit) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also not very detailed, so this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Bybit', 'spot', 'derivatives', 'perpetuals', and 'leverage', but misses common user terms like 'crypto trading', 'order', 'futures', 'margin', 'API', or 'exchange account'.	2 / 3
Distinctiveness Conflict Risk	Clearly identifies Bybit as the specific exchange, which creates a distinct niche unlikely to conflict with other trading or crypto skills targeting different platforms.	3 / 3
	Total	8 / 12 Passed

Implementation

57%

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

The skill provides highly actionable, executable curl commands for Bybit API integration, which is its primary strength. However, it suffers from significant repetition in authentication headers, includes unnecessary marketing content (referral section), and lacks proper workflow sequencing for dangerous financial operations. The monolithic structure with no progressive disclosure makes it token-inefficient.

Suggestions

Extract repeated curl header patterns into a reusable helper function or reference, and move detailed endpoint examples to a separate REFERENCE.md file to reduce the monolithic structure.

Remove the referral/commission marketing section and the 'Popular Trading Pairs' table — these waste tokens on information that doesn't help Claude execute tasks.

Add an explicit trading workflow with validation checkpoints: check balance → calculate position size → display order preview → await user confirmation → execute → verify order status → report result.

Create a clear feedback loop for error handling: if order fails, check error code → apply solution from error table → retry or escalate to user.

Dimension	Reasoning	Score
Conciseness	The skill has significant repetition in curl commands (identical header blocks repeated 8+ times) and includes unnecessary tables like 'Popular Trading Pairs' and 'Order Types' that explain things Claude already knows. The referral/commission section is marketing fluff that wastes tokens. However, the code examples themselves are reasonably lean.	2 / 3
Actionability	The skill provides fully executable bash/curl commands with proper authentication, specific API endpoints, jq parsing, and concrete parameter examples. Every operation is copy-paste ready with real endpoint URLs and request structures.	3 / 3
Workflow Clarity	Safety rules mention verifying balance and confirming before execution, but there's no actual workflow showing the sequence (e.g., check balance → display order preview → confirm → execute → verify). For trading operations involving real money and leverage, the lack of explicit validation checkpoints and feedback loops caps this at 2.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with all API endpoints inline. At ~180 lines, the reference tables, multiple order type examples, and error codes could be split into separate files. There are no internal references to supporting documents, and the content is not structured for progressive discovery.	1 / 3
	Total	8 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	9 / 11 Passed

Repository: Demerzels-lab/elsamultiskillagent
Commit: f45fcb5

Reviewed: 21 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.