Tessl • The management layer for AI agent skills

Blog Docs Log inGet started

SkillPublic

lighter

Lighter — Orderbook DEX on Arbitrum

Quality

64%

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/lighter/SKILL.md

Quality

Content

80%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 well-structured and highly actionable with concrete, copy-paste-ready commands and good section organization. Its main weakness is the absence of validation/confirmation steps for destructive batch trading operations, which limits workflow clarity.

Suggestions

Add a confirmation checkpoint before batch/destructive operations, e.g. prompt to confirm '/lighter closeall' and '/lighter cancelall' before executing.

Add a pre-check for '/lighter close <market>' to verify an open position exists and the market is valid before attempting the close.

Add a post-trade verification step such as running '/lighter positions' after opening a position to confirm the fill.

Dimension	Reasoning	Score
Conciseness	The body is lean, using command tables and short examples without explaining what a DEX or orderbook is, fitting 'Efficient; minor instances of over-explanation that could be trimmed'; it is not 5 because the same commands recur across Quick Start, Commands tables, and Examples.	4 / 5
Actionability	Commands are fully executable and copy-paste ready (e.g. '/lighter long ETH-USD 1 3000' for a limit order), with examples covering market/limit longs, shorts, and closes, matching 'Fully executable; copy-paste ready; specific examples cover the common cases'.	5 / 5
Workflow Clarity	A rough sequence exists (set credentials, check markets, get price, trade) but there are no validation checkpoints for destructive/batch operations like '/lighter closeall' and '/lighter cancelall', which per the rubric caps workflow_clarity at 3; it is not 4 because the validation gaps are material.	3 / 5
Progressive Disclosure	The skill is self-contained with no bundle files and well-organized sections (Quick Start, Commands grouped by category, Configuration, Resources) giving easy navigation, matching the simple-skill exception for clear single-purpose content; it is not lower because nothing is buried or nested.	5 / 5
	Total	17 / 20 Passed

Description

32%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 a minimal product tagline: it identifies the niche clearly but provides no concrete actions and no 'when to use' guidance. It would rarely surface for a natural user request without relying on the /lighter command name.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user wants to trade perpetuals on Lighter or check Arbitrum perp markets'.

List concrete actions in the description, e.g. 'trade perpetual futures, open/close positions, view orderbooks, and check balances on Lighter'.

Include natural user-facing trigger terms like 'perps', 'perpetuals', and 'Lighter DEX' so it matches how users actually phrase requests.

Dimension	Reasoning	Score
Specificity	The description "Orderbook DEX on Arbitrum" names the domain but lists no concrete actions, matching the anchor 'Names the domain but actions are minimal or generic'; it is not a 1 because the domain is concretely specified rather than abstract.	2 / 5
Completeness	It gives only a vague 'what' (a product category) and entirely omits any 'when'/Use-when guidance, matching 'Has a vague what and no when'; the missing trigger clause caps completeness at 3, but the 'what' here is too thin to reach that.	2 / 5
Trigger Term Quality	It offers only the category label (orderbook, DEX, Arbitrum) with no natural user phrases such as 'trade perps', 'open positions', or 'Lighter', fitting 'One or two generic keywords; missing the natural phrases users say' rather than 3 which requires broader keyword coverage.	2 / 5
Distinctiveness Conflict Risk	Naming a specific protocol (Lighter) on a specific chain (Arbitrum) carves a clear niche with minor overlap risk against other DEX/trading skills, fitting 'Mostly distinct; minor overlap risk'; it is not 5 because no explicit triggers are given.	4 / 5
	Total	10 / 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/lighter/SKILL.md
Revision: c930628

Reviewed: 1 month ago

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.

lighter

Table of Contents

Is this your skill?