drift-sdk
Drift Protocol perpetual futures trading on Solana (direct SDK)
74
63%
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/drift-sdk/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, distinctive niche (Drift Protocol perpetual futures on Solana) but fails to provide actionable detail. It lacks specific capabilities (what actions can be performed) and completely omits usage triggers (when Claude should select this skill). The technical specificity helps with distinctiveness but hurts accessibility for users who might use different terminology.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Drift', 'perps on Solana', 'perpetual futures', 'Solana derivatives trading', or 'DeFi leverage'
List specific concrete actions such as 'open/close positions', 'set leverage', 'manage collateral', 'query account balances', 'place limit orders'
Include common user terminology variations like 'perps', 'derivatives', 'leverage trading', 'DeFi trading' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Drift Protocol, perpetual futures trading, Solana) and mentions SDK usage, but doesn't list specific concrete actions like 'open positions', 'set leverage', 'manage margin', or 'close trades'. | 2 / 3 |
Completeness | Only addresses 'what' at a high level (perpetual futures trading on Drift/Solana) but completely lacks any 'when' guidance - no 'Use when...' clause or explicit trigger conditions. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Drift Protocol', 'perpetual futures', 'Solana', and 'SDK', but misses common variations users might say like 'perps', 'derivatives', 'trading bot', 'DeFi trading', or 'leverage trading'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche - Drift Protocol on Solana with direct SDK is highly distinctive and unlikely to conflict with other skills. The combination of protocol name, blockchain, and implementation method creates clear boundaries. | 3 / 3 |
Total | 8 / 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-structured, concise skill that provides clear command references for Drift Protocol trading. The actionability is excellent with copy-paste ready examples. The main weakness is the lack of validation/verification workflows for financial operations - no guidance on confirming trades executed, checking for errors, or handling edge cases in a domain where mistakes are costly.
Suggestions
Add a validation workflow section showing how to verify trades executed successfully (e.g., check positions after /drift long, verify order status after limit orders)
Include error handling guidance for common failure scenarios (insufficient margin, RPC errors, order rejection)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting commands in tables and code blocks without explaining what Solana or perpetual futures are. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | Provides copy-paste ready commands with concrete examples showing exact syntax for all operations. The command tables with descriptions and bash examples are immediately executable. | 3 / 3 |
Workflow Clarity | While individual commands are clear, there's no validation workflow for trading operations. Missing guidance on checking order status after placement, verifying position changes, or handling failed transactions - important for financial operations. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (Quick Start, Commands, Configuration, Features, Markets, Resources). External documentation is linked appropriately. Content is appropriately sized for a single file without needing splits. | 3 / 3 |
Total | 11 / 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
2a8c94e
- 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.