drift
Drift Protocol - perpetuals and prediction markets on Solana
49
37%
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/SKILL.mdQuality
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 list any concrete actions the skill performs and entirely omits guidance on when Claude should select it. It needs significant expansion to be useful for skill selection among multiple options.
Suggestions
Add concrete actions the skill performs, e.g., 'Opens and closes perpetual positions, places prediction market bets, queries account balances and open orders on Drift Protocol.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about trading perpetuals on Drift, placing prediction market bets, or interacting with Drift Protocol on Solana.'
Include common trigger term variations such as 'perps', 'DeFi trading', 'Drift SDK', 'Solana trading', and 'open position' to improve matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Drift Protocol, perpetuals, prediction markets, Solana) but lists no concrete actions. There are no verbs describing what the skill does—it reads more like a tagline than a capability description. | 1 / 3 |
Completeness | The description barely answers 'what does this do' (only implies a domain) and completely lacks any 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | It includes some natural keywords a user might say: 'Drift', 'perpetuals', 'prediction markets', 'Solana'. However, it misses common variations like 'perps', 'trading', 'DeFi', 'open position', 'place bet', or 'Drift Protocol SDK'. | 2 / 3 |
Distinctiveness Conflict Risk | Mentioning 'Drift Protocol' specifically is fairly distinctive, but the vague framing ('perpetuals and prediction markets on Solana') could overlap with other Solana DeFi or trading skills without clearer action-based differentiation. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
52%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is concise and well-structured as a quick reference card for Drift slash commands, but it lacks critical depth for safe execution. Trading operations are inherently risky and the absence of any validation steps, error handling, or confirmation workflows is a significant gap. Additionally, it's unclear what system or tool actually processes these slash commands, making the actionability questionable.
Suggestions
Add validation/confirmation workflows for trading operations (e.g., confirm order details before submission, check balance before trading, verify position before closing)
Clarify the execution context—what tool or integration processes these /drift commands, and how Claude should handle errors or failed transactions
Add guidance on risk constraints such as maximum position sizes, slippage tolerance, and what to do when orders fail or partially fill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what Drift is beyond one line, no padding about Solana or perpetual futures concepts. Every line serves a purpose. | 3 / 3 |
Actionability | Provides clear command syntax with examples, but these are slash commands without any underlying code, SDK usage, or implementation details. It's unclear how Claude would actually execute these commands—there's no connection to an API, SDK, or tool. | 2 / 3 |
Workflow Clarity | No workflow sequencing for multi-step trading operations. Trading involves risky/destructive financial operations but there are no validation steps, no confirmation flows, no error handling guidance, and no feedback loops for failed orders or insufficient balance scenarios. | 1 / 3 |
Progressive Disclosure | Content is well-organized into logical sections (Commands, Examples, Market Types), but for a protocol with perpetuals, prediction markets, and multiple market types, there are no references to deeper documentation for advanced topics like order types, risk management, or API details. | 2 / 3 |
Total | 8 / 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
e71a5f6
- 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.