drift

Drift Protocol - perpetuals and prediction markets on Solana

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/drift/SKILL.md

Quality

Content

72%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.

A lean, well-structured command reference with concrete executable slash commands and examples; its main weakness is the absence of validation/checkpoint steps for the destructive trading operations it exposes.

Suggestions

Add validation checkpoints before risky actions, e.g. verify the market index exists and confirm balance/margin before "/drift long" with leverage.

Specify parameter units for <size> and the leverage <amount> so commands are unambiguous.

Clarify the relationship between the "spot" market type and the trading commands, which currently only reference -PERP markets.

Dimension	Reasoning	Score
Conciseness	The body is compact command tables with inline annotations and a short examples block, assuming Claude knows what perps/Solana are; the only trimming candidate is the opening line that restates the description, keeping it just below the lean/5 anchor.	4 / 5
Actionability	Concrete copy-paste slash commands with parameter placeholders and worked examples (e.g. "/drift long SOL-PERP 0.5") cover common cases, but units for <size> and <amount> are unspecified, a minor gap that keeps it below 5.	4 / 5
Workflow Clarity	Commands are listed clearly but this is a catalog of destructive financial operations (leveraged perp positions, cancel, leverage) with no validation checkpoints (e.g. confirm margin, verify market index), so the destructive-operation cap holds it at 3.	3 / 5
Progressive Disclosure	The skill is under 50 lines, self-contained with no bundle files, and organized into clear sections (Commands / Examples / Market Types), meeting the simple-skill exception for a top score on organization alone.	5 / 5
	Total	16 / 20 Passed

Description

40%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 identifies a distinct, well-scoped domain but is essentially a label: it states no concrete actions and provides no "Use when" trigger guidance, leaving both the what and the when underspecified.

Suggestions

Add concrete actions, e.g. "Open and close positions, manage orders, set leverage on Drift."

Add an explicit trigger clause, e.g. "Use when the user wants to trade perpetuals or prediction markets on Drift."

Include natural synonyms users say, such as "perps" and "futures", alongside "perpetuals".

Dimension	Reasoning	Score
Specificity	The description "Drift Protocol - perpetuals and prediction markets on Solana" names a specific domain but provides no concrete actions (no verbs like trade, open, or close), fitting the "names the domain but actions are minimal or generic" anchor rather than the entirely-vague anchor below it.	2 / 5
Completeness	It offers only a vague "what" (identifying the protocol without stating what it does) and entirely lacks a "when"/"Use when" trigger clause, matching the "vague what and no when" anchor; the missing trigger guidance caps it below 3.	2 / 5
Trigger Term Quality	It includes relevant terms ("perpetuals", "prediction markets", "Solana", "Drift Protocol") but omits common natural variations traders actually say, most notably "perps", "futures", and "trading", so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	Naming a specific protocol on a specific chain ("Drift Protocol ... on Solana") gives it a clear niche with minimal conflict risk, but the absence of explicit trigger phrases leaves minor overlap risk with other Solana/trading skills, placing it just below 5.	4 / 5
	Total	11 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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/SKILL.md
Commit: 715fd4a

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