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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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

The body is highly actionable with executable code, clear workflows, and explicit validation checkpoints. Its weaknesses are length and redundancy across the hardening/policy/best-practices sections, and progressive disclosure is undercut by missing example bundle files and inline API reference that should be split out.

Suggestions

Create the referenced ./examples/swap.md, lend.md, trigger.md, and price.md files (or remove the dead links) so the Complete Working Examples section resolves to real bundle content.

Move the per-API playbooks (endpoints, error-code tables, gotchas) into per-family reference files and keep SKILL.md as a routing overview with one-level-deep links, improving progressive disclosure.

Consolidate the overlapping Rate Limits, Production Hardening, Integration Best Practices, and Fresh Context Policy sections to remove repeated rate-limit and retry guidance and tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is dense and almost entirely Jupiter-specific detail Claude would not know, but it is lengthy with redundancy: rate-limit guidance recurs in the Swap playbook, Rate Limits section, and Production Hardening, and the Fresh Context Policy, Integration Best Practices, and Production Hardening sections overlap. Not a 1 (no generic concept padding) but not a 3 (could be tightened).	2 / 3
Actionability	Provides fully executable TypeScript helpers (jupiterFetch, signAndSend, jupiterAction, withRetry), concrete endpoint paths, and specific copy-paste-ready gotchas like 'token.audit?.isSus === true', matching the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	The Intent Router sequences intent to first action, the Fresh Context Policy gives a numbered fetch-then-execute sequence, per-API Flow lines (e.g. Studio create-tx -> upload -> sign -> submit) are explicit, and validation/feedback checkpoints are present ('Fail fast if x-api-key missing', 'reconcile submitted vs confirmed vs failed', re-quote before execution).	3 / 3
Progressive Disclosure	External developers.jup.ag refs are well-signaled and one-level, but the per-API playbooks and endpoint enumerations are inline content that could be split into files, and the referenced ./examples/*.md files do not exist in the bundle, so the structure is only partly organized rather than a clean overview-to-detail split.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 is specific, complete, and clearly scoped to the Jupiter API domain with an explicit Use clause and natural trigger terms. It does not pad with fluff and uses third-person voice throughout.

Dimension	Reasoning	Score
Specificity	Enumerates 12 concrete API families (Swap, Lend, Perps, Trigger, Recurring, Tokens, Price, Portfolio, Prediction Markets, Send, Studio, Lock, Routing) plus four specific use categories (endpoint selection, integration flows, error handling, production hardening), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly states what it does ('Comprehensive guidance for integrating Jupiter APIs') and when to use it via an explicit 'Use for endpoint selection, integration flows, error handling, and production hardening' clause, satisfying both what AND when.	3 / 3
Trigger Term Quality	Family names double as natural user terms (swap, lend, perps, price, portfolio, limit order, dca) and are the phrases a user would say when needing this skill; coverage is broad rather than relying on internal jargon.	3 / 3
Distinctiveness Conflict Risk	Narrowly scoped to Jupiter APIs with named sub-products and Jupiter-specific triggers, making it unlikely to be selected for unrelated skills.	3 / 3
	Total	12 / 12 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
Commit: 21b72ce

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