Name: integrating-jupiter
Rating: 70.39999999999999 (1 reviews)
Author: jup-ag

integrating-jupiter

Comprehensive guidance for integrating Jupiter APIs (Swap, Lend, Perps, Trigger, Recurring, Tokens, Price, Portfolio, Prediction Markets, Send, Studio, Lock, Routing). Use for endpoint selection, integration flows, error handling, and production hardening.

Quality

88%

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

The canonical home for this skill is integrating-jupiter in jup-ag/agent-skills

Quality

Content

82%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 highly actionable, well-structured reference skill with executable code, exact endpoints, and strong error-handling feedback loops. Its weaknesses are minor redundancy in error-handling code and references, and dead ./examples/ links that point to bundle files which do not exist.

Suggestions

Create the referenced ./examples/{swap,lend,trigger,price}.md files or inline the end-to-end examples directly so the 'Complete Working Examples' links are not dead ends.

De-duplicate error handling: fold the Cross-Cutting jupiterAction/withRetry block into the Quickstart helper, or clearly differentiate their roles to remove overlap.

Trim the Operational References list to entries not already linked as Refs in the individual playbooks to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	Dense and information-rich, assuming Claude's competence (no padding about what Solana/DeFi/Jupiter is), with every playbook earning its place. Minor trim opportunities exist: error handling appears twice (jupiterFetch in Quickstart plus the jupiterAction/withRetry Cross-Cutting block) and several Refs are repeated in the Operational References section.	4 / 5
Actionability	Fully executable guidance: copy-paste TypeScript quickstart helper, exact base URLs and HTTP methods per endpoint, parameter-level details (decimals, slippageBps), and a retryable error-code table with concrete actions. Specific examples cover the common cases.	5 / 5
Workflow Clarity	Clear top-level sequence via the Intent Router (first action per intent) plus explicit flows for Swap, Trigger, and Studio, and validation/retry feedback loops in Production Hardening and the error table. Some playbooks (Tokens, Price, Portfolio) are reference-style endpoint lists without explicit step sequencing or checkpoints, which keeps it just below a 5.	4 / 5
Progressive Disclosure	Well-organized into clear sections with one-level-deep, clearly-signaled external references (Refs blocks to developers.jup.ag). The main gap is the 'Complete Working Examples' section linking to ./examples/swap.md, lend.md, trigger.md, price.md — files that are not present in the bundle (no examples/ directory), creating dead navigation links, and Operational References duplicates some playbook Refs.	4 / 5
	Total	17 / 20 Passed

Description

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

A strong, specific description that names the domain, enumerates the full API surface, and provides an explicit 'Use for...' trigger clause. Its only gap is trigger-term breadth — natural synonyms like 'trade', 'buy/sell', 'quote', and 'limit order' appear in the body but not the description.

Suggestions

Add a 'Use when the user mentions swap, trade, buy/sell, quote, limit order, DCA, or Jupiter/jup.ag' clause to broaden natural trigger coverage.

Consider adding file/extension-style anchors (e.g., 'jup.ag', 'Jupiter API') more prominently as user-mentionable phrases.

Dimension	Reasoning	Score
Specificity	Names the Jupiter domain and enumerates 12 concrete API families (Swap, Lend, Perps, Trigger, Recurring, Tokens, Price, Portfolio, Prediction Markets, Send, Studio, Lock, Routing) plus concrete integration actions (endpoint selection, integration flows, error handling, production hardening), giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what ('Comprehensive guidance for integrating Jupiter APIs...') and when ('Use for endpoint selection, integration flows, error handling, and production hardening') with concrete trigger guidance, satisfying the equivalent-explicit-trigger requirement.	5 / 5
Trigger Term Quality	Good keyword coverage via the API family names users naturally say in DeFi ('swap', 'lend', 'perps', 'trigger', 'price'), but missing common natural synonyms and variations such as 'trade', 'buy', 'sell', 'quote', 'limit order', 'dca' that the body itself lists.	4 / 5
Distinctiveness Conflict Risk	Jupiter-specific niche with explicit family enumeration and a 'Use for...' clause scoped to Jupiter integration; minimal conflict risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 4 missing	Warning

	Total	14 / 16 Passed

Repository: jup-ag/agent-skills
Path: .plugins/integrate-jupiter/claude/skills/integrating-jupiter/SKILL.md
Commit: a2211e3

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