drift
Drift Protocol - perpetuals and prediction markets on Solana
Overall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a tagline rather than a functional skill description. It identifies the domain (Drift Protocol on Solana) but fails to specify what actions Claude can perform or when this skill should be selected. Without concrete capabilities or trigger guidance, Claude would struggle to appropriately select this skill from a larger skill library.
Suggestions
Add specific actions Claude can perform, e.g., 'Query positions, place perpetual orders, check funding rates, analyze prediction market outcomes'
Add explicit trigger guidance: 'Use when the user mentions Drift, perpetual futures, perps on Solana, or prediction markets on Drift'
Include common user terminology variations like 'perps', 'futures trading', 'DeFi trading', 'leverage trading on Solana'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain (Drift Protocol, perpetuals, prediction markets, Solana) but lists no concrete actions. It doesn't specify what Claude can actually do with this skill - no verbs or capabilities are mentioned. | 1 / 3 |
Completeness | Only partially answers 'what' (names the domain but not actions) and completely missing 'when' - no 'Use when...' clause or explicit trigger guidance exists. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords users might say ('Drift', 'perpetuals', 'prediction markets', 'Solana'), but missing common variations like 'perps', 'futures', 'trading', 'DeFi', or specific actions users might request. | 2 / 3 |
Distinctiveness Conflict Risk | The specific mention of 'Drift Protocol' provides some distinctiveness, but could overlap with general Solana skills or other DeFi/trading skills. The lack of specific actions makes it harder to distinguish from similar blockchain trading skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is highly concise and well-organized for a command reference. However, it lacks workflow guidance for trading operations (which involve financial risk) and doesn't clarify the execution context for these slash commands. The absence of validation/confirmation steps for potentially costly trading operations is a notable gap.
Suggestions
Add a brief workflow section showing a typical trading flow with validation (e.g., check balance -> place order -> verify position)
Clarify the execution context - what tool or interface processes these /drift commands
Add expected output examples for key commands like /drift positions to show what responses look like
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Drift is beyond a one-line description. Every line serves a purpose - command syntax, examples, or market types. | 3 / 3 |
Actionability | Commands are clearly documented with syntax, but these are slash commands rather than executable code. Missing details on how to actually execute these (what tool/interface), error handling, or what responses look like. | 2 / 3 |
Workflow Clarity | Commands are listed but no workflow guidance for multi-step trading operations. No validation steps mentioned (e.g., checking balance before trading, confirming order execution, handling failed transactions). | 2 / 3 |
Progressive Disclosure | For a simple skill under 50 lines, the organization is appropriate. Clear sections for commands, examples, and market types. No need for external references given the scope. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
91%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 | |
- 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.