jupiter

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

Quality

52%

Does it follow best practices?

Impact

—

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

Content

64%

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

This skill provides strong actionability with concrete commands, real code examples, and complete API usage patterns for Jupiter DEX operations. However, it suffers from redundancy across its commands/examples/tools sections and critically lacks validation or confirmation workflows for financial transactions. The content would benefit from being split into a concise overview with references to detailed API/tool documentation.

Suggestions

Add validation/confirmation steps before executing swaps and financial operations (e.g., get quote first, confirm slippage, verify amounts before executing)

Consolidate the commands, examples, and tools sections to reduce redundancy — the examples section could replace the commands section entirely

Split the tool reference tables and full TypeScript API into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with key examples

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some redundancy — the commands section, examples section, and tools table all overlap significantly. The features bullet list adds little value since the features are already demonstrated. The tool tables largely restate what the commands and API sections already convey.	2 / 3
Actionability	Provides fully executable TypeScript code with real mint addresses, concrete command examples with inline comments explaining intent, and complete API imports. The environment variables section gives copy-paste ready configuration.	3 / 3
Workflow Clarity	For a skill involving financial transactions (swaps, limit orders, DCA), there are no validation checkpoints, no error handling guidance, no confirmation steps before executing swaps, and no mention of checking quotes before executing. Missing feedback loops for destructive financial operations caps this at 2.	2 / 3
Progressive Disclosure	The content is well-structured with clear sections and headers, but it's quite long and monolithic. The tool reference tables and full API examples could be split into separate reference files. No external file references are used despite the content length warranting them.	2 / 3
	Total	9 / 12 Passed

Description

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 niche (Jupiter DEX on Solana) with some specific operations listed, giving it good distinctiveness. However, it lacks a 'Use when...' clause entirely and could benefit from more natural trigger terms and expanded capability details. It reads more like a tagline than a functional skill description.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to swap tokens on Solana, set up limit orders, or configure dollar-cost averaging (DCA) strategies via Jupiter.'

Include more natural trigger term variations such as 'token swap', 'trade tokens', 'dollar cost averaging', 'SOL trading', 'Solana DEX', and 'exchange tokens'.

Expand the capability list with more specific actions like 'find optimal swap routes', 'configure slippage tolerance', 'schedule recurring purchases', or 'query token prices'.

Dimension	Reasoning	Score
Specificity	Names the domain (Jupiter DEX aggregator on Solana) and lists some actions (swaps, limit orders, DCA), but doesn't elaborate on what each entails or list more granular capabilities like token pair selection, slippage configuration, or route optimization.	2 / 3
Completeness	Describes what the skill does (Jupiter DEX aggregator operations) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also fairly thin, warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Jupiter', 'DEX', 'swaps', 'limit orders', 'DCA', and 'Solana' which users might naturally say, but misses common variations like 'token swap', 'dollar cost averaging', 'trading', 'exchange', 'SOL', or 'swap tokens'.	2 / 3
Distinctiveness Conflict Risk	Very clearly scoped to Jupiter DEX on Solana with specific DeFi operations (swaps, limit orders, DCA), making it highly unlikely to conflict with other skills. The combination of platform (Jupiter), blockchain (Solana), and specific operation types creates a distinct niche.	3 / 3
	Total	8 / 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: 2 months 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.