jupiter

Jupiter DEX aggregator - swaps, limit orders, and DCA on Solana

Quality

63%

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

Quality

Discovery

40%

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 clear, specific domain (Jupiter DEX on Solana) with distinct terminology that reduces conflict risk. However, it lacks explicit trigger guidance ('Use when...') and could benefit from expanded natural language terms users might say when needing this skill. The actions listed are too brief to fully convey the skill's capabilities.

Suggestions

Add a 'Use when...' clause specifying triggers like 'when user wants to swap tokens on Solana', 'trade on Jupiter', or 'set up recurring purchases'

Expand trigger terms to include natural variations: 'token swap', 'exchange tokens', 'trade crypto', 'dollar cost averaging', 'Jup'

Elaborate on specific capabilities: 'Execute token swaps with best price routing, create limit orders at target prices, set up recurring DCA purchases'

Dimension	Reasoning	Score
Specificity	Names the domain (Jupiter DEX aggregator on Solana) and lists some actions (swaps, limit orders, DCA), but these are brief and not fully elaborated with concrete details about what each action entails.	2 / 3
Completeness	Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Jupiter', 'DEX', 'swaps', 'limit orders', 'DCA', and 'Solana' that users might say, but missing common variations like 'token swap', 'exchange', 'trade', 'dollar cost averaging', or 'aggregator'.	2 / 3
Distinctiveness Conflict Risk	Very specific niche - Jupiter DEX on Solana is a distinct platform with clear triggers (Jupiter, Solana, DEX aggregator) that are unlikely to conflict with other skills.	3 / 3
	Total	8 / 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 well-crafted skill that efficiently documents Jupiter DEX operations with concrete, executable examples and clear command syntax. The main weakness is the lack of validation/verification steps for financial operations - users should know how to confirm swaps succeeded, check order fills, or handle failures. The structure and conciseness are excellent.

Suggestions

Add a 'Verification' section showing how to confirm swap success (e.g., check transaction signature, verify balance changes)

Include error handling guidance for common failure scenarios (insufficient balance, slippage exceeded, order not filled)

Add a workflow example showing the full flow: quote -> verify quote -> execute -> confirm execution

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient, presenting commands, examples, and API references without explaining what Jupiter, DEXes, or DCA concepts are. Every section adds actionable value without padding.	3 / 3
Actionability	Provides fully executable TypeScript code examples with real mint addresses, concrete command syntax with examples, and complete tool tables. Users can copy-paste the code directly.	3 / 3
Workflow Clarity	Commands and examples are clear, but there's no validation guidance for financial operations. Missing feedback loops for checking swap success, order status verification, or error handling for failed transactions.	2 / 3
Progressive Disclosure	Well-organized with clear sections (Commands, Examples, Features, Tools, API, Environment). Content is appropriately structured for a single skill file without needing external references for this scope.	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: 2a8c94e

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