Name: integrating-jupiter
Rating: 68 (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

85%

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

78%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, dense integration reference with executable code, precise endpoint/error semantics, and clear routing workflows. Its weaknesses are progressive disclosure (monolithic inlining of 13 playbooks plus broken example-file references) and minor conciseness redundancy.

Suggestions

Create the referenced ./examples/swap.md, lend.md, trigger.md, and price.md files (or remove the dead links), since the 'Complete Working Examples' section currently points to non-existent files.

Split the 13 inlined API playbooks into one-level-deep reference files (e.g. references/swap.md, references/trigger.md) and keep SKILL.md as a routing overview pointing to them, rather than a ~400-line monolith.

De-duplicate rate-limit guidance (it appears in both the Swap section and the Rate Limits section) and trim the single ~50-term triggers line to the highest-signal terms to recover tokens.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude knows Solana/web3 without over-explaining concepts, but it has minor redundancy (rate-limit guidance repeated in the Swap section and the Rate Limits section) and the ~50-term single-line triggers list is bloated, keeping it just below the lean anchor.	4 / 5
Actionability	It provides copy-paste-ready TypeScript helpers (jupiterFetch, signAndSend, jupiterAction, withRetry), exact endpoint paths and base URLs, an error-code table mapping each code to a concrete retry action, and field-level gotchas (e.g. token.audit?.isSus === true).	5 / 5
Workflow Clarity	The Intent Router table sequences intent to API family to first action, per-API playbooks give ordered first actions, and withRetry/jupiterAction plus the Fresh Context Policy and Production Hardening checklists provide validation and feedback loops, but the bulk of the playbooks are reference-style endpoint/gotcha lists rather than full validate-fix-retry workflows.	4 / 5
Progressive Disclosure	Headers and the Intent Router give reasonable structure, but ~400 lines of inlined API reference across 13 families could be split into separate reference files, and the ./examples/swap.md\|lend.md\|trigger.md\|price.md links are broken (no examples/ directory or any references/scripts/assets bundle exists), so references are signaled but non-functional.	3 / 5
	Total	16 / 20 Passed

Description

87%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, third-person description that clearly states both what it covers (13 Jupiter API families) and when to use it, anchored to a distinct provider niche. The only soft spot is that the action verbs are abstract categories rather than concrete operations.

Dimension	Reasoning	Score
Specificity	Names the domain and several specific action areas ('endpoint selection, integration flows, error handling, and production hardening') plus 13 API families, but the actions are abstract categories rather than concrete verbs like 'extract, fill, merge', leaving minor gaps versus the comprehensive anchor.	4 / 5
Completeness	It explicitly answers both 'what' ('Comprehensive guidance for integrating Jupiter APIs') and 'when' via an explicit 'Use for endpoint selection, integration flows, error handling, and production hardening' clause with concrete triggers.	5 / 5
Trigger Term Quality	Product names (Swap, Lend, Perps, Trigger, Price, Portfolio) are natural DeFi terms users would say, giving good keyword coverage, but it lacks synonyms and file extensions so it falls short of the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	'Jupiter APIs' is a clear provider-specific niche with distinct product triggers, giving minimal conflict risk with other skills.	5 / 5
	Total	18 / 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/codex/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.