CtrlK
BlogDocsLog inGet started
Tessl Logo

jupiter-swap-migration

Migration guide from Jupiter Metis (v1) or Ultra to Swap API v2. Use when migrating existing Jupiter swap integrations, updating base URLs, or transitioning from quote+swap-instructions to the unified build endpoint.

64

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is well-organized and reasonably concise with concrete endpoint and parameter guidance, a clear sequenced migration checklist, and good progressive-disclosure intent. Its main weakness is that the referenced ./examples/*.md files are missing from the bundle, which breaks navigation and leaves the body without the promised executable before/after code.

Suggestions

Add the missing ./examples/ultra-to-order.md, ./examples/metis-to-build.md, and ./examples/metis-to-order.md files (or inline minimal before/after code snippets) so the referenced before/after examples actually resolve and the body has executable code.

Tighten or externalize the long inline Triggers list to reduce token overhead in the main body.

Add an explicit validation feedback loop to the checklist (e.g., 'if the devnet swap fails, diff the request against the v1 request and re-run') to strengthen the verification step for this batch migration.

DimensionReasoningScore

Conciseness

The body is lean and information-dense with no padding about what Jupiter is or how APIs work; the main verbosity is the very long inline Triggers list, which could be trimmed or externalized.

4 / 5

Actionability

Gives concrete endpoint paths and exact parameter/field renames, but the promised before/after code examples live only in linked ./examples/*.md files that do not exist in the bundle, leaving no executable code in the body itself.

3 / 5

Workflow Clarity

The 10-step Post-Migration Checklist is clearly sequenced with a URL-audit step and a final end-to-end verification step, though the validation feedback loop is only weakly implied rather than an explicit validate→fix→retry cycle.

4 / 5

Progressive Disclosure

Structure is well-intended — overview with clearly signaled one-level-deep references to per-path example files — but the three ./examples/*.md links resolve to no files in the bundle, so navigation is broken despite the clear signaling.

3 / 5

Total

14

/

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.

The description is specific, complete, and well-scoped, clearly answering both what the skill does and when to use it with concrete trigger phrases. It is slightly technical-jargon-heavy in its keyword coverage, but otherwise strong.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'migrating existing Jupiter swap integrations, updating base URLs, or transitioning from quote+swap-instructions to the unified build endpoint' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what ('Migration guide from Jupiter Metis (v1) or Ultra to Swap API v2') and when ('Use when migrating existing Jupiter swap integrations, updating base URLs, or transitioning from quote+swap-instructions to the unified build endpoint') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes good domain keywords ('Jupiter Metis (v1)', 'Ultra', 'Swap API v2', 'quote+swap-instructions', 'unified build endpoint') that migrating users would say, but is somewhat technical-term-heavy and lacks broader natural synonyms.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Jupiter swap migration from Metis/Ultra to v2) with distinct triggers and explicit scope boundaries that steer new integrations to a different skill, minimizing conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 3 missing

Warning

Total

14

/

16

Passed

Repository
jup-ag/agent-skills
Reviewed

Table of Contents

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.