drift-sdk

Drift Protocol perpetual futures trading on Solana (direct SDK)

Quality

52%

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/drift-sdk/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 and distinctive niche (Drift Protocol perpetual futures on Solana via SDK), which helps with distinctiveness. However, it lacks specific concrete actions (e.g., place orders, manage positions, check funding rates) and entirely omits a 'Use when...' clause, making it incomplete for skill selection purposes.

Suggestions

Add a 'Use when...' clause with trigger terms like 'Use when the user wants to trade perpetual futures on Drift Protocol, open/close positions, place limit orders, or interact with Drift on Solana'.

List specific concrete actions such as 'Place market and limit orders, manage open positions, query funding rates, check account balances, and liquidate positions on Drift Protocol'.

Include common user-facing synonyms and variations like 'perps', 'perp trading', 'DeFi trading', 'Drift DEX', and 'Solana trading'.

Dimension	Reasoning	Score
Specificity	Names the domain (Drift Protocol perpetual futures trading on Solana) and hints at the method (direct SDK), but does not list specific concrete actions like placing orders, managing positions, querying balances, etc.	2 / 3
Completeness	Provides a partial 'what' (perpetual futures trading) but completely lacks any 'when' clause or explicit trigger guidance. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Drift Protocol', 'perpetual futures', 'Solana', and 'SDK' which users might mention, but misses common variations like 'perps', 'trading bot', 'open position', 'limit order', or 'DeFi'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Drift Protocol', 'perpetual futures', 'Solana', and 'direct SDK' creates a very specific niche that is unlikely to conflict with other 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 is well-organized and concise, providing a clean command reference for Drift Protocol trading. However, it falls short on actionability by presenting slash commands rather than actual SDK code despite claiming 'Direct SDK' integration, and lacks validation/error-handling workflows critical for financial trading operations. The incomplete markets table and unexplained advanced order types represent missed opportunities for progressive disclosure.

Suggestions

Add actual SDK code examples (TypeScript/Python) showing connection initialization, trade execution, and error handling — or clarify that this is a CLI/tool wrapper rather than 'Direct SDK' usage.

Add validation checkpoints to the workflow: check balance before trading, verify position opened successfully, check health factor before increasing leverage.

Complete the Markets table or link to a separate MARKETS.md reference file instead of using '...' placeholder.

Document error scenarios and recovery steps (e.g., transaction failures, insufficient margin, RPC timeouts) given the financial risk involved.

Dimension	Reasoning	Score
Conciseness	The content is lean and well-structured. It avoids explaining what Drift Protocol or Solana are in detail, assumes Claude's competence, and uses tables and code blocks efficiently. Every section earns its place.	3 / 3
Actionability	The commands are clearly documented with examples, but this is a slash-command reference rather than executable SDK code. Despite the title mentioning 'Direct SDK,' there's no actual SDK code (e.g., TypeScript/Python initialization, connection setup, or trade execution code). The commands are copy-paste ready but only within an assumed tool/CLI context that isn't fully explained.	2 / 3
Workflow Clarity	The Quick Start provides a basic sequence (set credentials → check balance → trade → close), but there are no validation checkpoints, no error handling guidance, no feedback loops for failed transactions, and no mention of checking health factor before opening leveraged positions. For a financial trading skill involving potentially destructive operations, missing validation caps this at 2.	2 / 3
Progressive Disclosure	The content is reasonably organized with clear sections and tables, and links to external resources. However, the Markets table is incomplete (uses '...') without pointing to a reference file, and there's no separation of advanced topics (e.g., order types like post-only/IOC/FOK are mentioned in Features but never explained or linked to documentation).	2 / 3
	Total	9 / 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: e71a5f6

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