CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

drift-sdk

Drift Protocol perpetual futures trading on Solana (direct SDK)

56

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/drift-sdk/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and well-structured with copy-paste commands, but its financial/batch operations lack validation checkpoints, capping workflow clarity. The incomplete Markets table and inline reference material leave minor organization gaps.

Suggestions

Add explicit validation/confirmation checkpoints before destructive or batch actions, e.g. verify position and confirm with the user before `/drift close` / `closeall` / `cancelall`, and check the health factor before opening leveraged positions.

Complete or remove the placeholder '...' rows in the Markets table, or move the full market list to a reference file.

Trim the marketing language in the intro ('Solana's leading', 'Bypass the gateway requirement') to a single factual sentence.

DimensionReasoningScore

Conciseness

The body is mostly lean — command tables, a config block, and a features list with no padding about what Solana or perps are — but the intro ('Solana's leading perpetual futures DEX', 'Bypass the gateway requirement') is mildly promotional and could be trimmed, matching 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

It provides fully executable, copy-paste-ready commands with concrete examples (`/drift long BTC 0.1`, `/drift short ETH 1 2500`, env var exports) covering the common trading cases.

5 / 5

Workflow Clarity

A rough sequence exists (set credentials -> check balance -> open -> close), but destructive and batch operations (`closeall`, `cancelall`, opening leveraged positions) have no explicit validation or confirmation checkpoints, so workflow clarity is capped at 3 per the rubric.

3 / 5

Progressive Disclosure

Content is well organized into clearly signaled sections (Quick Start, Commands, Configuration, Features, Markets) with no nested references, though the Markets table is left incomplete ('...') and all content is inline with no bundle files to offload the reference material.

4 / 5

Total

16

/

20

Passed

Description

52%Weight 40%Scale 1-5

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 is distinctive and names a clear niche, but it is light on concrete capabilities and omits any 'when to use' trigger guidance. Adding specific actions and a 'Use when...' clause would lift the weakest dimensions.

Suggestions

Add concrete actions, e.g. 'Open long/short positions, set leverage, and manage orders on Drift Protocol perpetual futures via direct SDK'.

Append a trigger clause such as 'Use when the user wants to trade perps on Drift, open/close positions, or manage leverage on Solana'.

Include natural synonyms users say ('perps', 'leverage', 'long/short') alongside 'perpetual futures'.

DimensionReasoningScore

Specificity

The description names the domain ('Drift Protocol perpetual futures trading on Solana') and a method ('direct SDK'), but the only action verb is the generic 'trading' with no concrete actions like opening positions, setting leverage, or managing orders, matching the 'names domain but actions are minimal' anchor.

2 / 5

Completeness

It gives a clear 'what' (perp futures trading on Drift via direct SDK) but has no 'Use when...' or equivalent trigger clause, so per the rubric a missing explicit trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

It includes relevant niche keywords ('Drift Protocol', 'perpetual futures', 'Solana', 'SDK') a trader would say, but misses common variations/synonyms like 'perps', 'leverage', 'long/short', placing it at 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

The niche is sharply defined — Drift Protocol perps on Solana via direct SDK — with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

alsk1992/CloddsBot

Path

src/skills/bundled/drift-sdk/SKILL.md

Revision

c930628

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill