bybit
Bybit exchange integration. Trade spot, derivatives, and perpetuals with up to 100x leverage.
62
Quality
52%
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 ./public/skills/0xterrybit/bybit/SKILL.mdQuality
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) with some specific product types, making it distinctive. However, it lacks explicit trigger guidance ('Use when...') and misses common user terminology for crypto trading. The description would benefit from more concrete actions and natural keywords users would actually say.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Bybit', 'crypto trading', 'futures trading', 'margin trading', or 'cryptocurrency exchange'
Expand specific actions beyond just 'trade' to include 'place orders', 'check balances', 'manage positions', 'set stop-losses', 'view market data'
Include common user terminology variations like 'crypto', 'futures', 'margin', 'long/short', 'BTC', 'USDT' that users naturally say when needing this skill
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Bybit exchange) and some actions (trade spot, derivatives, perpetuals), but doesn't list comprehensive concrete actions like placing orders, checking balances, managing positions, or setting stop-losses. | 2 / 3 |
Completeness | Describes what it does (Bybit trading integration) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Bybit', 'spot', 'derivatives', 'perpetuals', and 'leverage', but misses common variations users might say like 'crypto trading', 'futures', 'margin trading', 'long/short positions', or 'cryptocurrency exchange'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly specific to Bybit exchange with distinct product types (spot, derivatives, perpetuals) and the 100x leverage detail; unlikely to conflict with other exchange integrations or general trading skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, executable API examples for Bybit trading operations with proper authentication handling. However, it includes unnecessary marketing content (referral section), lacks explicit validation workflows critical for financial operations, and could benefit from splitting reference material into separate files. The safety rules are present but not integrated into actionable workflows.
Suggestions
Remove or minimize the referral code section - it adds no actionable value and wastes tokens on marketing content
Add an explicit trading workflow with validation checkpoints: 1) Check balance → 2) Display order preview → 3) Get user confirmation → 4) Execute → 5) Verify execution result
Move reference tables (trading pairs, order types, categories, error codes) to a separate REFERENCE.md file and link to it
Remove the Features bullet list - it describes capabilities without providing actionable guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary content like the referral code section (marketing fluff), feature bullet lists that don't add actionable value, and tables explaining basic concepts like order types that Claude already knows. | 2 / 3 |
Actionability | Provides fully executable curl commands with proper authentication, signature generation, and jq parsing. All code examples are copy-paste ready with clear variable substitution patterns. | 3 / 3 |
Workflow Clarity | Safety rules mention verification steps but there's no explicit workflow showing the sequence (check balance → display order → confirm → execute → verify). For trading operations involving financial risk, the validation checkpoints should be more explicit with feedback loops. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but it's a long monolithic file. API reference details, error codes, and trading pair lists could be split into separate reference files with links from the main skill. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%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
45f9fac
- 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.