tessl-skill-index-evals/jup-ag__agent-skills__integrating-jupiter
Comprehensive guidance for integrating Jupiter APIs (Ultra Swap, Lend, Perps, Trigger, Recurring, Tokens, Price, Portfolio, Prediction Markets, Send, Studio, Lock, Routing).
86
Quality
84%
Does it follow best practices?
Impact
91%
1.85xAverage score across 5 eval scenarios
Discovery
57%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 effectively identifies a clear niche (Jupiter APIs) with specific product names, making it distinctive. However, it lacks explicit trigger guidance ('Use when...') and relies on technical API names rather than natural user language. The action verbs are generic development terms rather than concrete Jupiter-specific operations.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when building Solana DeFi applications, implementing token swaps, or integrating Jupiter exchange functionality.'
Include natural trigger terms users might say: 'Solana swap', 'DeFi integration', 'token exchange', 'crypto trading API', 'Jupiter SDK'.
Replace generic actions with concrete examples: 'Execute token swaps, fetch real-time prices, create limit orders, manage perpetual positions' instead of 'endpoint selection, integration flows'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific API names (Ultra Swap, Lend, Perps, etc.) and mentions actions like 'endpoint selection, integration flows, error handling, and production hardening', but these are somewhat generic development concepts rather than concrete actions specific to Jupiter APIs. | 2 / 3 |
Completeness | Clearly describes what it does (guidance for integrating Jupiter APIs with various capabilities), but lacks an explicit 'Use when...' clause. The when is only implied through the context of Jupiter API work. | 2 / 3 |
Trigger Term Quality | Includes 'Jupiter APIs' and specific API names which are relevant keywords, but misses natural user phrases like 'Solana swap', 'DeFi integration', 'token trading', or 'crypto exchange API' that users might actually say when needing this skill. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific to Jupiter APIs with named products (Ultra Swap, Lend, Perps, etc.), making it clearly distinguishable from generic API or blockchain skills. Unlikely to conflict with other skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exceptionally well-crafted skill that serves as a comprehensive routing document for Jupiter API integration. It maximizes information density through tables, structured playbooks, and executable code while maintaining clear navigation via the Intent Router and consistent reference linking. The skill demonstrates mastery of progressive disclosure by providing actionable summaries with clear paths to detailed documentation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely efficient use of tokens - tables, code blocks, and bullet points convey maximum information with minimal prose. No explanations of concepts Claude already knows (Solana, TypeScript, APIs). Every section earns its place. | 3 / 3 |
Actionability | Provides fully executable TypeScript code for the quickstart, complete with error handling patterns. Each API section includes specific endpoints, HTTP methods, and concrete parameters. The cross-cutting error pattern is copy-paste ready. | 3 / 3 |
Workflow Clarity | Intent Router table provides clear decision tree for first action. Each API playbook specifies the exact sequence (e.g., 'GET /order -> sign -> POST /execute'). Studio flow explicitly sequences create-tx -> upload -> sign -> submit. Validation checkpoints embedded in Production Hardening section. | 3 / 3 |
Progressive Disclosure | Excellent structure with overview-level playbooks linking to detailed refs (Overview, OpenAPI specs, specific docs). References are one level deep and clearly signaled with markdown links. Content appropriately split between quick reference here and detailed docs externally. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%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 | |
Install with Tessl CLI
npx tessl i tessl-skill-index-evals/jup-ag__agent-skills__integrating-jupiterReviewed
Table of Contents