lighter

Lighter — Orderbook DEX on Arbitrum

Quality

55%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/lighter/SKILL.md

Quality

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 title rather than a functional description. It identifies the protocol and chain but provides zero information about what actions the skill performs or when Claude should select it. It would be nearly impossible for Claude to reliably choose this skill from a large pool based on this description alone.

Suggestions

Add concrete actions the skill performs, e.g., 'Places limit and market orders, queries orderbook depth, retrieves trade history on the Lighter DEX.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user wants to trade on Lighter, place orders on Arbitrum orderbook DEX, check Lighter liquidity, or interact with the Lighter protocol.'

Include common user-facing synonyms and variations such as 'swap', 'trade', 'limit order', 'decentralized exchange', and 'on-chain trading' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names a specific protocol ('Lighter') and platform ('Arbitrum') but describes no concrete actions. There are no verbs indicating what the skill does—no 'trade', 'place orders', 'query liquidity', etc.	1 / 3
Completeness	The description answers neither 'what does this do' (no actions described) nor 'when should Claude use it' (no 'Use when...' clause or equivalent trigger guidance). It is essentially just a label.	1 / 3
Trigger Term Quality	It includes some relevant keywords a user might say: 'Lighter', 'Orderbook', 'DEX', and 'Arbitrum'. However, it misses common variations like 'swap', 'trade', 'limit order', 'market order', 'liquidity', or 'decentralized exchange'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Lighter' as a specific protocol and 'Arbitrum' as a specific chain provides some distinctiveness, but without action-level detail it could overlap with any other Arbitrum DEX skill or general DeFi skill.	2 / 3
	Total	6 / 12 Passed

Implementation

87%

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

This is a clean, well-structured command reference skill that is highly concise and actionable. Its main weakness is the lack of validation/verification steps for trading operations — there's no guidance on confirming trades executed correctly, checking for errors, or handling edge cases like insufficient balance. For a skill involving financial transactions, explicit feedback loops would significantly improve safety.

Suggestions

Add a verification step after trading commands (e.g., 'After opening a position, run `/lighter positions` to confirm execution and check fill price')

Add error handling guidance or common failure modes (e.g., insufficient balance, market not found, order rejected)

Dimension	Reasoning	Score
Conciseness	Every token earns its place. No unnecessary explanations of what an orderbook DEX is, no padding about Arbitrum or perpetual futures beyond the one-line description. Tables and code blocks are tight and informative.	3 / 3
Actionability	Commands are concrete, copy-paste ready with clear syntax patterns. Examples show both market and limit orders with specific parameters. Configuration is explicit with environment variable names.	3 / 3
Workflow Clarity	The quick start provides a reasonable sequence (set credentials → check markets → get price → trade), but there are no validation checkpoints or feedback loops for trading operations. No guidance on checking order status after placement, verifying position opened correctly, or handling errors — important for financial/destructive operations.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections (Quick Start → Commands → Configuration → Resources). External docs are linked for deeper reference. The skill is under 50 lines of effective content and appropriately self-contained with one-level-deep references.	3 / 3
	Total	11 / 12 Passed

Validation

90%

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 — 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: 11 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.